CRJCA0146E The Lifecycle Project Administration (LPA) application could not communicate with the application at the following URL
Juan Martín Alberti (20●14●17)
| asked Dec 16 '13, 10:47 p.m.
edited Dec 17 '13, 7:39 a.m. by Paul Slauenwhite (8.4k●1●2)
Hi there.
I'm getting this error when runing admin/setup on a Jazz Team Server:
CRJCA0146E The Lifecycle Project Administration (LPA) application could not communicate with the application at the following URL: https://server:9443/qm/friends. To communicate across servers with other applications, the LPA application must be able to communicate with the application at the specified URL
Jazz Team Server si configured to run with rtc, rm and qm.
The strange thing is that Consumers Inbound in jts/admin are:
/admin be00540c9763486596317bbec688713d lpa_user Trusted
/ccm bea501d238744509b97601bba6cc3832 ccm_user Trusted
/qm 857d61721d4042dd93b36777a42adf5b qm_user Trusted
/qm 1dfe07de27e94a8cb09ebdbd83933cd2 qm_user Trusted
/rm 3f1ccb50eb014cb295a780a9d744901c rm_user Trusted
And the Friends Outbound on qm/admin are:
Change and Configuration Management (/ccm) https://server:9443/ccm/rootservices 963e723694a84780933ccfa6ce4bc858
Jazz Team Server https://server:9443/jts/rootservices 1dfe07de27e94a8cb09ebdbd83933cd2
Requirements Management (/rm) https://server:9443/rm/rootservices 8a46929dba75427fa2507b5e47320383
As you can see /qm is registered twice.
/qm with the id 857d61721d4042dd93b36777a42adf5b it isn't on qm/admin friends outbound list and it's the entry that Jazz Team Server doesn't allow to delete.
Another error that we get that i supose that is related with the same thing is:
CRJZS0218E The server has not found anything matching the Request-URI.
And we're getting this error when we go to /admin/web/members (Create Lifecycle Project > Members)
Any idea of what this can be? Thanks.
|
4 answers
|
Kot,
The %JazzTeamServer%/server/conf/admin/admin.properties says:
|
|
Thanks Kot.
I checked all:
- The QM application is listed on Registered Applications.
- Clicking on the drop down next to the 'Home' icon on the top left of the screen, QM projects are listed properly (no error messages)
- No errors regarding server communication in both JTS and QM diagnostics page
- No distributed environment. All applications (JTS, CCM, RM and QM in the same server)
I detected a strange thing when i execute the command "repotools-jts -listStorageAreaKeys"
....
com.ibm.team.lpa.717a05f1-39dd-4ce3-8473-917f0f1d9b79,be00540c9763486596317bbec688713d
com.ibm.team.lpa.717a05f1-39dd-4ce3-8473-917f0f1d9b79.configs,be00540c9763486596317bbec688713d
com.ibm.team.lpa.717a05f1-39dd-4ce3-8473-917f0f1d9b79.index,be00540c9763486596317bbec688713d
com.ibm.team.lpa.717a05f1-39dd-4ce3-8473-917f0f1d9b79.projects,be00540c9763486596317bbec688713d
com.ibm.team.lpa.717a05f1-39dd-4ce3-8473-917f0f1d9b79.templates,be00540c9763486596317bbec688713d
com.ibm.team.lpa.a2e9c019-13fd-4695-b0ad-ca2edf343e09,be00540c9763486596317bbec688713d
com.ibm.team.lpa.a2e9c019-13fd-4695-b0ad-ca2edf343e09.configs,be00540c9763486596317bbec688713d
com.ibm.team.lpa.a2e9c019-13fd-4695-b0ad-ca2edf343e09.index,be00540c9763486596317bbec688713d
com.ibm.team.lpa.a2e9c019-13fd-4695-b0ad-ca2edf343e09.projects,be00540c9763486596317bbec688713d
com.ibm.team.lpa.a2e9c019-13fd-4695-b0ad-ca2edf343e09.templates,be00540c9763486596317bbec688713d
.....
As you can see the com.ibm.team.lpa lines appears twice. I compared to an installation of CLM that works fine and this lines appers once. Maybe this is related to the error.
I see this error in jts.log file:
2013-12-18 17:15:22,096 [ Thread-72] WARN org.apache.http.impl.client.DefaultHttpClient - Authentication error: Unable to respond to any of these challenges: {oauth=WWW-Authenticate: OAuth realm="https%3A%2F%2Fclmserver%3A9443%2Fjts", oauth_problem="invalid_consumer_key"}
I see this errors in qm.log file:
2013-12-18 16:15:45,640 [qm: AsynchronousTaskRunner-1 @@ 16:15] WARN com.ibm.rational.test.lm.service - ProviderService:ensureProviderImportOccurs AQXSP2504W The automation integration failed to initialize because the integration_config.xml file could not be loaded.
2013-12-18 16:23:55,355 [qm: AsynchronousTaskRunner-1 @@ 16:23] WARN com.ibm.rqm.defects.service - ChangeRequestCollector:hadInitialized AQXIN2503W Blocking defects cannot be automatically synchronized between the Quality Management application and the Change and Configuration Management (CCM) application. The integration of the applications is incorrectly configured.
I see this errors in admin.log file:
2013-12-18 15:36:20,133 [ WebContainer : 12] WARN com.ibm.team.lpa.applications - CRJCA0148E Artifact containers could not be retrieved from the following application: https://clmserver:9443/qm/rootservices. Artifact containers in this application cannot be displayed until this problem is resolved.
java.util.EmptyStackException
at java.util.Stack.peek(Stack.java:64)
at com.ibm.team.lpa.clients.ProcessXmlParser.endElement(ProcessXmlParser.java:261)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLNSDTDValidator.endNamespaceScope(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at com.ibm.team.lpa.common.clients.XmlResponseHandler.parse(XmlResponseHandler.java:88)
at com.ibm.team.lpa.common.clients.XmlResponseHandler.handleResponse(XmlResponseHandler.java:57)
at com.ibm.team.lpa.common.clients.CommonHttpClient.execute(CommonHttpClient.java:110)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:919)
at com.ibm.team.lpa.clients.ProjectAreaClient.getProjectAreas(ProjectAreaClient.java:41)
at com.ibm.team.lpa.services.ContextService.getContextModel(ContextService.java:127)
at com.ibm.team.lpa.services.ProjectService.getProjectModel(ProjectService.java:238)
at com.ibm.team.lpa.services.ProjectService.doGet(ProjectService.java:74)
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 com.ibm.team.lpa.common.services.AbstractLpaRestHandler.dispatch(AbstractLpaRestHandler.java:274)
at com.ibm.team.lpa.common.services.AbstractLpaRestHandler.handle(AbstractLpaRestHandler.java:330)
at com.ibm.team.jfs.app.servlet.AppContainerServlet.service(AppContainerServlet.java:285)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
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:120)
at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1224)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:774)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:456)
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:139)
at com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.java:172)
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.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:87)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:895)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:195)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:452)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:511)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:305)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:276)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.determineNextChannel(SSLConnectionLink.java:1049)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.readyInboundPostHandshake(SSLConnectionLink.java:717)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink$MyHandshakeCompletedCallback.complete(SSLConnectionLink.java:413)
at com.ibm.ws.ssl.channel.impl.SSLUtils.handleHandshake(SSLUtils.java:1066)
at com.ibm.ws.ssl.channel.impl.SSLHandshakeIOCallback.complete(SSLHandshakeIOCallback.java:87)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
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:1690)
2013-12-18 15:40:27,752 [ LPA Change Event Monitor] ERROR com.ibm.team.lpa.events - CRJCA0073E An error occurred while fetching change event feed from https://clmserver:9443/qm/service/com.ibm.team.repository.common.internal.IFeedService
com.ibm.team.jfs.app.http.HttpInternalServerErrorException: CRJCA0070E An unexpected error occurred while fetching change events.
at com.ibm.team.lpa.common.http.client.cache.ChangeEventClient$SyndFeedHandler.handleResponse(ChangeEventClient.java:79)
at com.ibm.team.lpa.common.http.client.cache.ChangeEventClient$SyndFeedHandler.handleResponse(ChangeEventClient.java:1)
at com.ibm.team.lpa.common.clients.CommonHttpClient.execute(CommonHttpClient.java:110)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:919)
at com.ibm.team.lpa.common.http.client.cache.ChangeEventClient.getFeed(ChangeEventClient.java:96)
at com.ibm.team.lpa.common.http.client.cache.ChangeEventMonitor$MasterRunnable.processChangeEvents(ChangeEventMonitor.java:282)
at com.ibm.team.lpa.common.http.client.cache.ChangeEventMonitor$AbstractRunnable.run(ChangeEventMonitor.java:216)
at com.ibm.team.lpa.common.http.client.cache.ChangeEventMonitor$1.run(ChangeEventMonitor.java:450)
at java.util.Timer$TimerImpl.run(Timer.java:296)
Caused by: com.sun.syndication.io.ParsingFeedException: Invalid XML: Error on line 36: The element type "link" must be terminated by the matching end-tag "</link>".
at com.sun.syndication.io.WireFeedInput.build(WireFeedInput.java:198)
at com.sun.syndication.io.SyndFeedInput.build(SyndFeedInput.java:123)
at com.ibm.team.lpa.common.http.client.cache.ChangeEventClient$SyndFeedHandler.handleResponse(ChangeEventClient.java:72)
... 8 more
Caused by: org.jdom.input.JDOMParseException: Error on line 36: The element type "link" must be terminated by the matching end-tag "</link>".
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:468)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:851)
at com.sun.syndication.io.WireFeedInput.build(WireFeedInput.java:194)
... 10 more
Caused by: org.xml.sax.SAXParseException: The element type "link" must be terminated by the matching end-tag "</link>".
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:453)
... 12 more
2013-12-18 16:16:02,691 [ WebContainer : 3] INFO com.ibm.team.lpa.config - CRJCA0037I Lifecycle Project Administration Build RJF-I20130515-1759
2013-12-18 16:16:03,221 [ WebContainer : 3] INFO com.ibm.team.lpa.config - com.ibm.team.lpa.app.jtsTargetHost=LpaInit.Default
2013-12-18 16:16:03,221 [ WebContainer : 3] INFO com.ibm.team.lpa.config - com.ibm.team.lpa.app.jtsVirtualHost=LpaInit.Default
2013-12-18 16:16:03,237 [ WebContainer : 3] INFO com.ibm.team.lpa.config - CRJCA0010I Project Administration application running at https://clmserver:9443/admin, using Jazz Team Server at https://clmserver:9443/jts/rootservices
Comments In the %JazzTeamServer%/server/conf/admin/admin.properties, which ID do you see for the 'com.ibm.team.jfs.app.context.storage.area.name' property? com.ibm.team.lpa.717a05f1-39dd-4ce3-8473-917f0f1d9b79 OR com.ibm.team.lpa.a2e9c019-13fd-4695-b0ad-ca2edf343e09 I suggest to collect output of ISALite (http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m1/index.jsp?topic=%2Fcom.ibm.team.concert.doc%2Ftopics%2Ft_using_the_isal.html) and engage Support. |
Hi Juan, I would check for the following to see whether QM is correctly registered with the JTS: - In /jts/admin > Home page, scroll down to the end of the page and see if there is a section for the QM application listed there - Clicking on the drop down next to the 'Home' icon on the top left of the screen, check whether QM projects are listed properly (if it shows any error messages) - Whether there are any error regarding server communication in both JTS and QM diagnostics page. - In case of distributed environment, ensure that you can reach /jts/admin from the QM server and vice versa. - Review jts.log and qm.log |
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.