It's all about the answers!

Ask a question

Issue sending team invitations


Fernando Bustamante (1) | asked Jan 18 '11, 6:57 p.m.
Hello.
I've installed RTC 3.0 with no problems and I've created a new project area, but when I try to send team invitations I'm getting the following error:

Error generating team invitations for the following members: AAA BBB.

com.ibm.team.repository.common.TeamRepositoryException
com.ibm.team.process.internal.service.ProcessService.sendTeamInvitation(ProcessService.java:4072)
com.ibm.team.process.internal.service.GenerateTeamInvitationOperation.run(GenerateTeamInvitationOperation.java:52)
com.ibm.team.process.internal.service.ProcessService.overrideProcess(ProcessService.java:1476)
com.ibm.team.process.internal.service.ProcessService.executeProcessItemSaveOperation(ProcessService.java:1397)
com.ibm.team.process.internal.service.ProcessService.generateTeamInvitation(ProcessService.java:3146)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
java.lang.reflect.Method.invoke(Method.java:600)
org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370)
org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356)
org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
$Proxy295.generateTeamInvitation(Unknown Source)
com.ibm.team.process.internal.service.web.ProcessRestService.generateTeamInvitation(ProcessRestService.java:2265)
com.ibm.team.process.internal.service.web.ProcessRestService.postGenerateTeamInvitations(ProcessRestService.java:2261)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
java.lang.reflect.Method.invoke(Method.java:600)
org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370)
org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356)
org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
$Proxy790.postGenerateTeamInvitations(Unknown Source)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
java.lang.reflect.Method.invoke(Method.java:600)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.doModelledRestService(AbstractTeamServerServlet.java:501)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest2(AbstractTeamServerServlet.java:1832)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest(AbstractTeamServerServlet.java:1688)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1598)
javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180)
org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:75)
javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120)
com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:62)
javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1655)
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:937)
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:500)
com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:91)
com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:864)
com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1583)
com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:183)
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:455)
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:384)
com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:83)
com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1772)
com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1550)
Caused by:
Error sending message.; nested exception is: com.ibm.team.repository.service.compatibility.util.http.CrossServerHttpClient$RestCommunicationException:
Bad Gateway (javax.mail.MessagingException)ID CRJAZ1611E
com.ibm.team.repository.service.compatibility.internal.mailer.MailerService.sendMail(MailerService.java:200)
com.ibm.team.repository.service.compatibility.internal.mailer.MailerService.sendMail(MailerService.java:187)
com.ibm.team.repository.service.compatibility.internal.mailer.MailerService.sendMail(MailerService.java:215)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
... 76 more.


The RTC application is using LDAP authentication, configured as Standalone LDAP in WebSphere Application Server.
This is our current configuration:

OS: Linux RH 5.3 32 bits
App Server: WAS 7.0.0.7
DB: DB2 v9.5.0.7
LDAP: MS AD 2008
SMTP Server: MS Exchange 2010

Any help appreciated

Thanks.

Fernando.

5 answers



permanent link
Qiong Feng Huang (76911610) | answered Jan 18 '11, 6:57 p.m.
JAZZ DEVELOPER
It looks like your SMTP server configured in RTC is not available. Please
make sure this server is available and configured correctly in RTC.

permanent link
Murali Dhandapani (11698) | answered Jan 25 '11, 4:15 a.m.
It looks like your SMTP server configured in RTC is not available. Please
make sure this server is available and configured correctly in RTC.




The configurations are correct but still gets the same error.

permanent link
Sourith Sisavath (211) | answered Jan 31 '11, 7:02 a.m.
You should check your configuration at
https://<Your>:<Your>/jts/admin#action=com.ibm.team.repository.admin.configureMailSettings

Make sure your SMTP is correct.
One way to debug is to use your own email address as "E-mail From Address"
Also, if your SMTP server does not require authentification, you should leave the field "SMTP Username" and "SMTP Password" blank.


It looks like your SMTP server configured in RTC is not available. Please
make sure this server is available and configured correctly in RTC.




The configurations are correct but still gets the same error.

permanent link
Martina Riedel (20323341) | answered Jun 23 '11, 1:38 p.m.
I have the same problem.
I have the exact same settings that work in RQM 2.x, the only difference on the screen is the new Transport Reuse Count field.

Did this ever get solved beyond the "check you settings"?
I have triple checked the settings, typed them in and and copied them over from RQM, no joy

permanent link
Martina Riedel (20323341) | answered Jun 23 '11, 3:40 p.m.
I have the same problem.
I have the exact same settings that work in RQM 2.x, the only difference on the screen is the new Transport Reuse Count field.

Did this ever get solved beyond the "check you settings"?
I have triple checked the settings, typed them in and and copied them over from RQM, no joy


After getting IT to allow the JTS box to send emails via smpt/Exchange, notification now works.
For all other apps, I got back the email bounce in the error message.
This is a really bad error message.

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.