JDBC Timeout

Question

Hi,
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?

Answer 1

Hi Jin-Chong,
We have that value set to 10800 which I believe is 3 hours.  We also set the timeout up top from 10 to 180, and upped the JVM Heap sizes.
<?xml version="1.0" encoding="utf-8"?><CrystalReportEngine-configuration>
    <timeout>180</timeout>
<IORFileLocation>${TEMP}</IORFileLocation>
<JavaServerTimeout>10800</JavaServerTimeout>
<JavaServerStartupTimeout>30</JavaServerStartupTimeout>
<JVMMaxHeap>512000000</JVMMaxHeap>
<JVMMinHeap>64000000</JVMMinHeap>
No luck with that though.  Still waiting from a response from SAP also, I think they will call me today.
I did some searching,  and I don't know if its related, but there is a timeout in the following file (on linux)
.../webapps/BOE/WEB-INF/eclipse/plugins/webpath.CrystalReports/web/WEB-INF/web.xml
    <!-- Define the default session timeout for your application,
        in minutes.  From a servlet or JSP page, you can modify
        the timeout for a particular session dynamically by using
        HttpSession.getMaxInactiveInterval().
    -->
    <session-config>
      <session-timeout>20</session-timeout>    <!-- 20 minutes for session objects -->
    </session-config>
Regards,
Sabir