I have got an error information CRJAZ1675E. But what does it mean?
I am using CLM version 5.0.1 on a Jazz webserver. In the Quality Management module in the Top ribbon you can choose 'Requirements'. If I click on that it tells me "Log in to view this content". If I click again then I get a very long error message:
Does anyone knows what this means and what should I do to correct it so that I can fix the problem?
The following problems occurred during the initialization process: com.ibm.team.jfs.app.http.HttpBadRequestException: CRJAZ1675E At least one service type must be specified at com.ibm.team.repository.service.internal.discovery.DiscoveryService.performQuery(DiscoveryService.java:479) at com.ibm.team.repository.service.internal.discovery.DiscoveryService.perform_GET(DiscoveryService.java:154) at com.ibm.team.repository.service.TeamRawService.service(TeamRawService.java:84) at sun.reflect.GeneratedMethodAccessor1292.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56) at com.sun.proxy.$Proxy1727.service(Unknown Source) at com.ibm.team.repository.servlet.AbstractTeamServerServlet.doRestService(AbstractTeamServerServlet.java:933) at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest2(AbstractTeamServerServlet.java:2283) at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest(AbstractTeamServerServlet.java:2079) at com.ibm.team.repository.servlet.AbstractTeamServerServlet.access$0(AbstractTeamServerServlet.java:2064) at com.ibm.team.repository.servlet.AbstractTeamServerServlet$1.service(AbstractTeamServerServlet.java:221) at com.ibm.team.repository.service.internal.compatibility.auth.DelegatedAuthHandler$1.run(DelegatedAuthHandler.java:229) at com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1718) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180) at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:126) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:76) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120) at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:74) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at com.ibm.team.repository.server.servletbridge.BridgeFilter.processDelegate(BridgeFilter.java:165) at com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.java:198) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:339) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:314) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:761) CRJAZ1675E At least one service type must be specified 400
Does anyone knows what this means and what should I do to correct it so that I can fix the problem?
Accepted answer
Martin,
I could not figure out what the reason for this error is either. See https://jazz.net/help-dev/CLMErrorMessages/index.jsp?topic=%2Fcom.ibm.messages.jazz.foundation%2FCRJAZ1675E.html
My interpretation is that there is a service discovery request against a server and there is no service specified.
I would consider creating an enhancement request to get the error description enhanced.
I could not figure out what the reason for this error is either. See https://jazz.net/help-dev/CLMErrorMessages/index.jsp?topic=%2Fcom.ibm.messages.jazz.foundation%2FCRJAZ1675E.html
My interpretation is that there is a service discovery request against a server and there is no service specified.
I would consider creating an enhancement request to get the error description enhanced.
4 other answers
Hello,
It seems the project association was somehow modified after the migration.
The workaround is to create the link between the RQM project and the RRC project again. Links should work after that.
Note that you may need to open RRC and remove the connection. Then add the RRC project from RQM > Manage This Project Area.
Also note that removing the project links does not remove the links in the actual artifacts.
I hope this helps.
Best regards,
Diane
It seems the project association was somehow modified after the migration.
The workaround is to create the link between the RQM project and the RRC project again. Links should work after that.
Note that you may need to open RRC and remove the connection. Then add the RRC project from RQM > Manage This Project Area.
Also note that removing the project links does not remove the links in the actual artifacts.
I hope this helps.
Best regards,
Diane
I had an instance where upgrade from 4.x to 5.x lead to the same error and it was resolved after removing and add the RQM-RM association again. The above solution worked !!!
But question is if there are many such projects linked, it will be tedious to achieve this.
Any suggestion to implement this on multiple projects in a single go?
Hi,
I just worked with a client with same error after an upgrade from 4.0.5 to 5.0.2.
In this case, there was a clear problem in the repotools-rm_rmUpdateProjectBackLinksOnline.log
2015-05-12 11:35:20,080 CRJAZ1357E The repotools command could not log in to the following server: https://clm-train.gomocean.info:9443/rm. Check the login credentials.
2015-05-12 11:35:20,080
java.lang.NullPointerException at com.ibm.rdm.repotools.commands.upgrade.backlinks.RMUpdateProjectBacklinksOnline$1RemoteServiceProvider.getService(RMUpdateProjectBacklinksOnline.java:111)
It looks like the rm server was not online when 'repotools-rm -rmUpdateProjectBackLinksOnline' was run during the upgrade.
We simply re-ran that command listed in the repotools log, e.g.
repotools-rm -rmUpdateProjectBackLinksOnline adminPassword=*********** adminUserId=jazzadmin repositoryURL=https://myrdngserver:9443/rm
and repotools can successfully, updating links for all projects. We were then able to access the requirements drop-down from all RQM project areas.
So, before you remove the association, if you just upgraded, ensure that 'repotools-rm -rmUpdateProjectBackLinksOnline' ran to completion.
Thanks,
Brett
I just worked with a client with same error after an upgrade from 4.0.5 to 5.0.2.
In this case, there was a clear problem in the repotools-rm_rmUpdateProjectBackLinksOnline.log
2015-05-12 11:35:20,080 CRJAZ1357E The repotools command could not log in to the following server: https://clm-train.gomocean.info:9443/rm. Check the login credentials.
2015-05-12 11:35:20,080
java.lang.NullPointerException at com.ibm.rdm.repotools.commands.upgrade.backlinks.RMUpdateProjectBacklinksOnline$1RemoteServiceProvider.getService(RMUpdateProjectBacklinksOnline.java:111)
It looks like the rm server was not online when 'repotools-rm -rmUpdateProjectBackLinksOnline' was run during the upgrade.
We simply re-ran that command listed in the repotools log, e.g.
repotools-rm -rmUpdateProjectBackLinksOnline adminPassword=*********** adminUserId=jazzadmin repositoryURL=https://myrdngserver:9443/rm
and repotools can successfully, updating links for all projects. We were then able to access the requirements drop-down from all RQM project areas.
So, before you remove the association, if you just upgraded, ensure that 'repotools-rm -rmUpdateProjectBackLinksOnline' ran to completion.
Thanks,
Brett