Error regristering ccm application on jts setup
When i try to register the ccm app (recognized automatically) in jts setup page (step6), it throws below error. Any pointers would help me to solve this problem.
Initially registration was succeeded with 9443 port. But when i change the port to standard default port 443 (to browse the URL without port) and re-register the app gives the problem. Error invoking registration handler for application "/ccm" at https://HOST/ccm/service/com.ibm.team.repository.service.internal.setup.IRegistrationHandlerServiceID CRJAZ1720E com.ibm.team.repository.common.TeamRepositoryException com.ibm.team.repository.service.internal.discovery.ApplicationRegistrationFriendRestService.postRegisterApp(ApplicationRegistrationFriendRestService.java:142) 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) $Proxy286.postRegisterApp(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.webapp.WebApp.handleRequest(WebApp.java:3826) com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:276) com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:931) com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1583) com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186) 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.HttpInboundLink.ready(HttpInboundLink.java:272) com.ibm.ws.ssl.channel.impl.SSLConnectionLink.determineNextChannel(SSLConnectionLink.java:1016) com.ibm.ws.ssl.channel.impl.SSLConnectionLink$MyReadCompletedCallback.complete(SSLConnectionLink.java:639) 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: Registration handler for application "/ccm" at https://HOST/ccm/service/com.ibm.team.repository.service.internal.setup.IRegistrationHandlerService failed with status 409 and response body "Error 409: A JTS friend entry for https://HOST:9443/jts/rootservices already exists. This application cannot also be registered with the JTS at https://HOST/jts/rootservices " (com.ibm.team.repository.common.TeamRepositoryException)ID CRJAZ1721E com.ibm.team.repository.service.internal.discovery.ApplicationRegistrationFriendRestService.notifyAppRegistrationHandler(ApplicationRegistrationFriendRestService.java:213) com.ibm.team.repository.service.internal.discovery.ApplicationRegistrationFriendRestService.postRegisterApp(ApplicationRegistrationFriendRestService.java:131) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48) ... 46 more. |
2 answers
The root cause of the error (down near the bottom, under "Caused by") explains it:
Registration handler for application "/ccm" at https://HOST/ccm/service/com.ibm.team.repository.service.internal.setup.IRegistrationHandlerService failed with status 409 and response body "Error 409: A JTS friend entry for https://HOST:9443/jts/rootservices already exists. This application cannot also be registered with the JTS at https://HOST/jts/rootservices " Since the application was already registered with the JTS at HOST:9443, it cannot also be registered with another JTS at HOST (using the default port). You should first delete the old friend entry for the JTS in the CCM "Friends (incoming)" section of the admin UI. |
|
Thanks for your valuable inputs. when i changed the ccm admin page,'Friends(Outbound)'-> Root Services URI to correct value, then i was able to register the \ccm application.
earlier, i tried to modify the Discovery URL, application type in jts admin page of Registered Applications didn't had succeeded. Thanks once again. |
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.