It's all about the answers!

Ask a question

java.net.SocketException when generating RPE report for DNGv6.0.1


Robert Huet (23112884) | asked Aug 12 '16, 12:15 p.m.
 I have created a test RPE template with source query of "usecasediagrams", which iterates across the datasource/artifact/aggregatedContent/aggregatedContentEntry, using the "about" element to create a dynamic data source for the resource in the diagram ("resources" api).  The report puts out the name of the use case diagram, and the name of each contained element (i.e. use case or actor).  Very simple stuff.  Works fine in the RRC 4.x environment.

However, when running in DNG 6.0.1 with RPE 2.1, I'm getting random java.netSocketExceptions when pulling from the dynamic data source ("resources" query).  This does not appear for every element, but just random ones, and appears as an INFO message in the RPE console but not in the rpe.log.  
INFO: I/O exception (java.net.SocketException) caught when processing request to {s}->https://jazzreporting:9443: Unrecognized Windows Sockets error: 0: socket write error
Aug 12, 2016 9:18:49 AM org.apache.http.impl.client.DefaultRequestDirector tryExecute
INFO: Retrying request to {s}->https://jazzreporting:9443
Aug 12, 2016 9:18:50 AM org.apache.http.impl.client.DefaultRequestDirector tryExecute

The RPE console shows a number of retries, and it seems to eventually pull the data (no issues invoking the REST call directly from the browser).  Sometimes the report succeeds, and sometimes it ends with the error: 
Invalid output state.

12-08-2016T10:51:43:203 [RRDG_1:64-CORE] CRRPE3012E IBM Rational Publishing Engine error.
Invalid output state.
com.ibm.rational.rpe.common.utils.RPEException: Invalid output state.
at com.ibm.rational.rpe.engine.output.OutputController.checkOutputState(OutputController.java:40)
at com.ibm.rational.rpe.engine.output.OutputController.begin(OutputController.java:51)
at com.ibm.rational.rpe.engine.core.executor.TemplateExecutor.processElement(TemplateExecutor.java:642)
at com.ibm.rational.rpe.engine.core.executor.TemplateExecutor.processElement(TemplateExecutor.java:711)
at com.ibm.rational.rpe.engine.core.executor.TemplateExecutor.processElement(TemplateExecutor.java:711)
at com.ibm.rational.rpe.engine.core.executor.TemplateExecutor.execute(TemplateExecutor.java:427)
at com.ibm.rational.rpe.engine.RRDGEngine.run(RRDGEngine.java:1251)
at java.lang.Thread.run(Thread.java:798)
I've been developing RPE reports for many years (most recently with v5.0.2 and RPE 1.2.1), so I'm concerned about this strange behavior with DNG 6.0.1 and RPE 2.1, especially since I have a number clients upgrading to 6.0.1 and 6.0.2.

Any ideas on how to further troubleshoot this issue would be greatly appreciated.
Thanks,
Robert

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.