It's all about the answers!

Ask a question

Getting error "failed to check application links" at Finalize Lifecycle Project Administration step in Jazz team server setup.


vikrant kamble (1323897) | asked Jan 20 '17, 6:02 a.m.
edited Jan 21 '17, 2:53 a.m.

 I am doing setup for jazz team server version 6.0.2. I have configured websphere application server using Interactive installation guide for CLM. I have installed DB2 database which is located on different system. I have registered all the required applications, tested database connection and created database tables. All the setup steps succeeded except for the step Finalize Lifecycle Project Administration. At this step I am getting error "failed to check application links."


I was able to finish setup even after this error is occurring but I could not sample lifecycle project(JKE Banking)
List of applications registered
ccm, dcc, gc, ldx, lqe, qm, relm, rm, rs
 
All the steps in jazz team server setup are successful except for this step.
How can I resolve the error?


Comments
vikrant kamble commented Jan 20 '17, 6:42 a.m.

 Screenshot of error I am getting


Arne Bister commented Jan 22 '17, 7:09 a.m.
JAZZ DEVELOPER

Can you please copy the detailed exception text that is indicated in your screenshot? Possibly the essential info is visible when you scroll down that text.

4 answers



permanent link
vikrant kamble (1323897) | answered Jan 23 '17, 3:40 a.m.

 Hi Arne,

It was problem related to QM,
CRJAZ2488E - The friend entry for the Jazz Team Server contains a consumer key that is invalid (it is not being accepted by the Jazz Team Server).

I unregistered the RQM, performed the JTS setup, error was resolved.


permanent link
vikrant kamble (1323897) | answered Jan 23 '17, 12:49 a.m.

 Hi Arne, detailed info of exception


com.ibm.team.repository.common.transport.TeamServiceException: Failed to check the application links. at com.ibm.team.lpa.app.services.FinalizeSetupService.areAppsLinked(FinalizeSetupService.java:315) at com.ibm.team.lpa.app.services.FinalizeSetupService.get(FinalizeSetupService.java:94) at com.ibm.team.lpa.common.services.AbstractLpaResource.perform_GET(AbstractLpaResource.java:61) at com.ibm.team.lpa.common.services.AbstractLpaRestService.perform_GET(AbstractLpaRestService.java:29) at com.ibm.team.repository.service.TeamRawService.service(TeamRawService.java:84) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) 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.$Proxy1390.service(Unknown Source) at com.ibm.team.repository.servlet.AbstractTeamServerServlet.doRestService(AbstractTeamServerServlet.java:971) at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest2(AbstractTeamServerServlet.java:2520) at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest(AbstractTeamServerServlet.java:2315) at com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1794) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) 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:668) at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:138) at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:74) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1227) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:776) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:458) at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:136) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:97) 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 com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:928) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1025) at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3761) at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:976) at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:200) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:459) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:526) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:312) at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:88) at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1784) at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175) at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161) at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138) at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204) at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775) at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1862) Caused by: java.lang.NullPointerException at com.ibm.team.repository.service.internal.oauth.shared.AuthenticatingClientService$4.close(AuthenticatingClientService.java:237) at com.ibm.team.lpa.app.services.FinalizeSetupService.getFriendsDocs(FinalizeSetupService.java:382) at com.ibm.team.lpa.app.services.FinalizeSetupService.areAppsLinked(FinalizeSetupService.java:297) ... 55 more 


permanent link
Arne Bister (2.6k12832) | answered Jan 23 '17, 3:21 a.m.
JAZZ DEVELOPER

Vikrant,

the key seems to be:
Caused by: java.lang.NullPointerException at com.ibm.team.repository.service.internal.oauth.shared.AuthenticatingClientService$4.close(AuthenticatingClientService.java:237)

buried in that long exception. There might be an issue with either a security certificate or firewall port.
You might want to check logfiles for JTS and possibly any proxy servers you use to find the root cause.
What ifix Level is your 6.0.2 installation?

- Arne


permanent link
Andy Wong (3133) | answered Jul 25 '17, 9:38 p.m.

Experience similar issue, in my case, I stop all Application Servers and start all Applications Servers in recommended order (ie: Stop JTS last, Start JTS first). As my problem may be due to the environment that I am working with is distributed App Servers, some App Servers has been reconfigured at some stage.

Hope this helps, if you experience similar issue, it is simple fix, good to try.

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.