Created On:  26 October 2010

Problem:

When the SQL statement has been executing for more than the busy-timeout value, you may receive the below error message
Online3 - [Mon May 31 15:05:06 EST 2010] stderr: WARNING : Rollback performed on BusyTimedOut connection
Online4 - [Mon May 31 14:52:39 EST 2010] stderr: WARNING : Rollback performed on BusyTimedOut connection

Resolution:

Root Cause: The "busyTimeout" default value is 600 seconds (10 minutes).
If the SQL statement is executing using the JDBC connection for more than the busy-timeout value, AppServer will rollback the transaction and re-claim the connection. The sample log snippet above will then show up if the logging is enabled. AppServer maintains a pool of JDBC connections. The busyTimeout value allows the AppServer to prevent the application from hogging the JDBC connection longer than necessary.

To avoid the warning, you can change the "busyTimeout" value to suit your application requirements. You can change the jndi-definition.xml in the default-resources.dar. 

       

Incident #2456491