WebLogic Server Retries and Spawns Rollback Request Threads Until Server is Out of Resources
(Doc ID 2827351.1)
Last updated on DECEMBER 20, 2023
Applies to:Oracle WebLogic Server - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On WLS 220.127.116.11 it noted that WebLogic retries rollback request until server instance is out of resources.
Scenario where one of the database queries doesn't complete within the duration specified by the JTA timeout (default is 600 seconds). As this transaction timed-out, WLS creates another execute thread, say T1, to rollback this transaction. However, this thread could not complete the rollback as the original thread (the one that is executing the query) holds a lock on the connection. The new thread (T1) waits for the original thread to release the lock (which doesn't happen immediately). Meanwhile, WLS keeps creating new execute threads T2, T3 etc while attempting to roll back the timed-out transaction, thereby slowing up the whole application server.
Thread dumps would show STUCK thread or multiple threads as below
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document