IBM WebSphere - Resolve "Transaction has timed out after x seconds"

by
Jeremy Canfield |
Updated: March 08 2022
| IBM WebSphere articles
Let's say the following is in the HPEL or SystemOut log
[6/11/18 9:15:54:983 CDT] 00000067 TimeoutManage I WTRN0006W: Transaction xxxxxxxx has timed out after 180 seconds.
One of the next events in the log should be WTRN0124I. This event identifies the source of the hang. In this example, the source of the hang is WebContainer. Another common source is ORB.thread.pool. The stack trace may identify a JDBC driver that is associated with the long running thread. In this example, an Oracle database connection is associated with the long running thread. When a database connection is associated, you will want to check the database for stalls or performance issues.
[6/11/18 9:15:54:983 CDT] 00000067 TimeoutManage I WTRN0124I: When the timeout occurred the thread with which the transaction is,
or was most recently associated was Thread[WebContainer : 37,5,main].
oracle.jdbc.driver.T4CDriverExtension.allocatePreparedStatement
oracle.jdbc.driver.PhysicalConnection.prepareStatement
oracle.jdbc.OracleConnectionWrapper.prepareStatement
Did you find this article helpful?
If so, consider buying me a coffee over at