What with this RRC error CRRRW7553E "The server returned this error code: 500" when create&print an artifact after upgrade to 4.0.6: fixed but how did we get there in the first place ?

long TRUONG

(365●4●123●147) Sep 23 '14, 7:17 p.m.

After upgrade to RRC 4.0.6, when trying to create & Print (no matter to PDF or doc format) any artifact, we got the error CRRRW7553E "An error has occurred while processing a server request. The server returned this error code: 500", as expanded below. We don't know yet if this option had been tried in the previous version 4.0.3, and if successful.

Have reproduced this on all 3 browsers: IE9, Chrome, Firefox.

We have now found technote 1654803 and fixed the issue in TEST env accordingly (cause 2). What we'd like to know is: What did we do wrong on the upgrade to both TEST and PRD env to get "The Publishing engine not initialized properly after the upgrade, getting error 500: Internal Server Error." on both.

Also, anybody else besides us getting into this ? The technote (dated 2014-04-16) listed:

Env:

Ubuntu 10.04
Mozilla Firefox

Software version: 4.0.1, 4.0.2, 4.0.3, 4.0.4

typical error line in rm.log: Line 3845: 2014-09-14 22:26:27,029 [ http-bio-443-exec-3126] ERROR .hp.hpl.jena.rdf.model.impl.RDFDefaultErrorHandler - file:///D:/IBM/rtc_406/JazzTeamServer/server/tomcat/bin/(line 1 column 1): Content is not allowed in prolog.

Could that error be related to the first line in the Java options for Tomcat, used for our DynaTrace:

-agentpath:d:\dlagent\dtagent.dll=name=Tomcat_RTC,server=<server>:<port>

An error has occurred while processing a server request. The server returned this error code: 500.

hide details

ID CRRRW7553E A message that was received from the server indicates an error with no specific handler.

Unable to load https://rtc-web1.ent.rt.csaa.com/rm/publish/print/requirement?resourceURI=https://rtc-web1.ent.rt.csaa.com/rm/resources/_D2QNgCvkEeOm_5QWe5ChCQ&formatURI=http://com.ibm.rdm/reports/formats/pdf&includeComments=true&showEmbedTitles=true&includeAttributes=true&maximiseEmbeds=true&projectURI=https://rtc-web1.ent.rt.csaa.com/jts/process/project-areas/_dTKnoFjjEeGQKPQbsGRGlw status: 500
Error: Unable to load https://rtc-web1.ent.rt.csaa.com/rm/publish/print/requirement?resourceURI=https://rtc-web1.ent.rt.csaa.com/rm/resources/_D2QNgCvkEeOm_5QWe5ChCQ&formatURI=http://com.ibm.rdm/reports/formats/pdf&includeComments=true&showEmbedTitles=true&includeAttributes=true&maximiseEmbeds=true&projectURI=https://rtc-web1.ent.rt.csaa.com/jts/process/project-areas/_dTKnoFjjEeGQKPQbsGRGlw status: 500 at Error (native) at new _6 (https://rtc-web1.ent.rt.csaa.com/rm/web/_js/?include=A~&etag=GJ0UER7jII2_en_GB&_proxyURL=%2Frm&ss=FFspe&locale=en-gb:2485:14) at _6 [as handleResponse] (https://rtc-web1.ent.rt.csaa.com/rm/web/_js/?include=A~&etag=GJ0UER7jII2_en_GB&_proxyURL=%2Frm&ss=FFspe&locale=en-gb:6183:4) at XMLHttpRequest._13 (https://rtc-web1.ent.rt.csaa.com/rm/web/_js/?include=A~&etag=GJ0UER7jII2_en_GB&_proxyURL=%2Frm&ss=FFspe&locale=en-gb:6198:5)

URL: https://rtc-web1.ent.rt.csaa.com/rm/publish/print/requirement?resourceURI=https://rtc-web1.ent.rt.csaa.com/rm/resources/_D2QNgCvkEeOm_5QWe5ChCQ&formatURI=http://com.ibm.rdm/reports/formats/pdf&includeComments=true&showEmbedTitles=true&includeAttributes=true&maximiseEmbeds=true&projectURI=https://rtc-web1.ent.rt.csaa.com/jts/process/project-areas/_dTKnoFjjEeGQKPQbsGRGlw

Error 500: Internal Server Error

java.lang.NullPointerException (More info found at entry [a52971665fb55c6e] in the RM application server log)

Requirements Management/4.0.6

0 votes

2 answers

4,443 views

0 votes

Accepted answer

Permanent link

Mike Jaworski

JAZZ DEVELOPER (1.4k●6) Sep 24 '14, 8:27 a.m.

Hi,

Whenever you upgrade to a new release of RRC, you will find that re-initializing the publish service is typically necessary to perform. This is because the reporting templates used by the publish service in your environment are deployed whenever /rm/publish/initialize is run, so once you upgrade (to 4.0.6 in this case), the deployed templates are still the same ones which were in use in your previous release (4.0.3 in your case). This is problematic because the data used by these templates changes between releases, so if you do not re-initialize the publish service after you upgrade, then the old templates being used could be looking for out-dated data formats, or else NOT looking for new data introduced in the new release.

If you'd like a more specific diagnosis, you could locate the entry in your log files denoted by the NullPointerException at ID "a52971665fb55c6e" and I could probably cross-reference the code and tell you exactly why it fails.

Hope this helps,

Mike Jaworski

long TRUONG selected this answer as the correct answer

0 votes

Comments

long TRUONG

Sep 24 '14, 3:11 p.m.

Thx Mike, we do appreciate a chance to learn more about the tools. Ah! Didn't realize that our q was cut short on the expansion too.

Will have to use the space for an answer to provide you with log entries for our last "create & print" artifact.

I have upgraded a few RRC along with the full CLM package, I guess this is the first time the upgraded version is used in earnest to run into this issue. I just wonder if the re-initialization shoud be included in the upgrade instructions (or is it already there, I just missed it ?) or included in the online RRC upgrade ?

One other answer

Permanent link

long TRUONG

(365●4●123●147) Sep 24 '14, 2:59 p.m.

@Mike: Here are:

The block you requested with ID "a52971665fb55c6e"
the rm.log full block of entries for our last action "create & print" an artifact (bottom section with ID Server Error: Entry [f1db96b732310cbc] )

2014-09-23 12:33:00,811 [ http-bio-443-exec-3878] ERROR ibm.rdm.fronting.server.rrs.publish.PublishService - Server Error: Entry [a52971665fb55c6e]

java.lang.NullPointerException

at com.ibm.rdm.fronting.server.rrs.publish.internal.PrintParameters.generateReportRequest(ArtifactPrinter.java:504)

at com.ibm.rdm.fronting.server.rrs.publish.internal.ArtifactPrinter.print(ArtifactPrinter.java:554)

at com.ibm.rdm.fronting.server.rrs.publish.internal.LegacyPublishService.doPost(LegacyPublishService.java:339)

at com.ibm.rdm.fronting.server.rrs.publish.internal.PublishServiceInternal.doPostInternal(PublishServiceInternal.java:50)

at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.runInternalMethod(RRSRestServiceBase.java:831)

at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.handleMethod(RRSRestServiceBase.java:710)

at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.doPost(RRSRestServiceBase.java:147)

at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.performService(RRSRestServiceBase.java:433)

at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.service(RRSRestServiceBase.java:239)

at com.ibm.team.jfs.app.servlet.AppContainerServlet.dispatchRequest(AppContainerServlet.java:159)

at com.ibm.team.jfs.app.servlet.AppContainerServlet.service(AppContainerServlet.java:285)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)

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:722)

at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120)

at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:74)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)

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 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)

at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)

at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)

at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)

at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)

at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:336)

at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)

at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)

at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1002)

at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)

at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:906)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:929)

at java.lang.Thread.run(Thread.java:761)

2014-09-23 12:35:39,017 [ http-bio-443-exec-3547] ERROR .hp.hpl.jena.rdf.model.impl.RDFDefaultErrorHandler - Premature end of file.

2014-09-23 12:35:39,018 [ http-bio-443-exec-3547] ERROR serPreferences.internal.UserPreferencesRestService - Server Error: Entry [566f3be4696caf0d]

com.hp.hpl.jena.shared.JenaException: org.xml.sax.SAXParseException: Premature end of file.

at com.hp.hpl.jena.rdf.model.impl.RDFDefaultErrorHandler.fatalError(RDFDefaultErrorHandler.java:60)

at com.hp.hpl.jena.rdf.arp.impl.ARPSaxErrorHandler.fatalError(ARPSaxErrorHandler.java:51)

at com.hp.hpl.jena.rdf.arp.impl.XMLHandler.warning(XMLHandler.java:211)

at com.hp.hpl.jena.rdf.arp.impl.XMLHandler.fatalError(XMLHandler.java:241)

at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(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.XMLDocumentScannerImpl$XMLDeclDispatcher.dispatch(Unknown Source)

at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)

at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)

at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)

at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)

at com.hp.hpl.jena.rdf.arp.impl.RDFXMLParser.parse(RDFXMLParser.java)

at com.hp.hpl.jena.rdf.arp.JenaReader.read(JenaReader.java)

at com.hp.hpl.jena.rdf.arp.JenaReader.read(JenaReader.java:160)

at com.hp.hpl.jena.rdf.arp.JenaReader.read(JenaReader.java:232)

at com.hp.hpl.jena.rdf.model.impl.ModelCom.read(ModelCom.java:235)

at com.ibm.rdm.fronting.server.services.userPreferences.internal.UserPreferencesDomainService.doPostInternal(UserPreferencesDomainService.java:79)