What extra configurations may be necessary for long running reports under IBM WebSphere?

Download PDF version of this faq: WebSphere_LongReports.pdf

Issue

When generating long running reports in excess of 3 minutes (greater than about 10MB) with IBM WebSphere and Parallel Crystal an error similar to the following could be thrown in the WebSphere console:

There were errors generated during processing your request: Error processing print job yourdomain.your.classes.YourAppException: com.mobileapps.pcre.PCREServerError: CORBA error: org.omg.CORBA.NO_RESPONSE: minor code: 0 completed: Maybe
Unknown error has occurred. Please report to the help desk if the problem persists

When you generate a long running report, WebSphere will force its underlying IBM Component Broker ORB to throw this exception if it does not receive a response (or the finished report) in about 3 minutes. So essentially WebSphere is waiting and when it does not get the report in this specified amount of time it times out by throwing the CORBA.NO_RESPONSE error.

Solution

Please refer to this link from IBM's web page, which offers guidance on how to set the com.ibm.CORBA.requestTimeout property in WebSphere. This property specifies the timeout period for responding to workload management requests.

http://www-4.ibm.com/software/webservers/appserv/doc/v35/ae/infocenter/was/070206.html