Skip to Content
Former Member
Sep 18, 2014 at 06:34 PM

JDBC Timeout



We are using a JDBC connection to Oracle for some reports we migrated from 3.1 to 4.0. All reports under about 20 minutes work fine, but when you hit the 20 minute mark, the report errors out. We had a similar issue in 3.1 that we fixed by adding a -RequestTimeout X (where X is milliseconds - 3600000 in our case) in the Crystal Job Server command line switch. (in addition to changing the timeout in CRConfig.xml) The Crystal Job Server doesn't seem to exist in 4.0, and adding it to the Adaptive Job Server command line doesn't work (the AJS ends up in failure status). Anyone know how to get similar behaviour to the -RequestTimeout in version 3.1?