Error CRJCA0073E every 5 minutes in SystemOut.log

I am also seeing this error in my recently installed 4.0.1 system.  JTS on one server, CCM and QM on remote servers.  LPA projects seem fine, all admin windows seem fine.  Its just the admin log that has this error in it for some reason.  Seems this service can't talk to my remote server for some reason.

 [      LPA Change Event Monitor] ERROR com.ibm.team.lpa.events                             - CRJCA0073E An error occurred while fetching change event feed from https://win7ultmt64b.ibm.com:9443/ccm/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:87)
   

Hi Ulf,
Have you tried visiting https://[hostname]:9443/jazz/service/com.ibm.team.repository.common.internal.IFeedService from web browser located on the server? Is it working correctly?

Ulf, Dave, could you provide entire stack trace of the error?

Hi Krzysztof,

Yes, the feed service is working fine. Of course when I open it in the browser I'll have to log in first.

See the stack trace below:

[4/3/13 9:09:03:821 CEST] 00000029 SystemOut     O 09:09:03,821 [LPA Change Event Monitor] ERROR com.ibm.team.lpa.events                             - CRJCA0073E An error occurred while fetching change event feed from https://sos-kpm.synobsys.local:9443/jazz/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:709)
    at com.ibm.team.lpa.common.http.client.cache.ChangeEventClient.getFeed(ChangeEventClient.java:96)
    at com.ibm.team.lpa.common.http.client.cache.ChangeEventMonitor$1.processChangeEvents(ChangeEventMonitor.java:200)
    at com.ibm.team.lpa.common.http.client.cache.ChangeEventMonitor$1.run(ChangeEventMonitor.java:155)
    at java.util.Timer$TimerImpl.run(Timer.java:293)
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)
    ... 7 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.JDOMException.<init>(JDOMException.java:112)
    at org.jdom.input.JDOMParseException.<init>(JDOMParseException.java:109)
    at org.jdom.input.SAXBuilder.build(SAXBuilder.java:418)
    at org.jdom.input.SAXBuilder.build(SAXBuilder.java:851)
    at com.sun.syndication.io.WireFeedInput.build(WireFeedInput.java:194)
    ... 9 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.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)
    ... 11 more

Hello,

Yes. And we get errors in de jts.log, but they are related to connections with other server (we have this RTC server connected to two other servers):

2013-03-30 00:35:15,307 [ jts: AsynchronousTaskRunner-0] ERROR service.internal.discovery.ServiceRegistrationTask  - CRJAZ1678E Error during service contribution registration from https://amss59.koopmanint.local:9443/jts/rootservices