It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,789
×7,386
×5,999
×343

question asked: Nov 20 '12, 5:07 a.m.
question was seen: 5,190 times
last updated: Apr 04 '13, 3:52 a.m.

Related questions

FAQ - How this Forum works

Error CRJCA0073E every 5 minutes in SystemOut.log

0
Ulf Buchner (318●22●13) | asked Nov 20 '12, 5:07 a.m.
edited Nov 20 '12, 5:08 a.m.
Hi all,

Every 5 minutes we get an error in the SystemOut.log.

[11/20/12 11:05:05:689 CET] 00000029 SystemOut O 11:05:05,689 [LPA Change Event Monitor] ERROR com.ibm.team.lpa.events - CRJCA0073E An error occurred while fetching change event feed from https://[hostname]:9443/jazz/service/com.ibm.team.repository.common.internal.IFeedService

Anyone has a clue what's happening here? Everything seems to work just fine.

Thanks & regards,

Ulf
Comments
Dave Bellagio commented Jan 10 '13, 10:20 p.m.

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)
   

Krzysztof Kaźmierczyk commented Apr 03 '13, 2:39 a.m.

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?

Ulf Buchner commented Apr 03 '13, 3:12 a.m. | edited Apr 03 '13, 3:13 a.m.

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

Marek Siekierski commented Apr 03 '13, 4:14 p.m.

Hello,


Have you always seen this error message in the logs? Are there any errors in the jts.log?

Ulf Buchner commented Apr 04 '13, 3:52 a.m.

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


We get this error for the two servers.

Be the first one to answer this question!

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.