Last updated on NOVEMBER 05, 2016
Applies to:Oracle Weblogic Server - Version 10.0 and later
Information in this document applies to any platform.
We have a scenario where WebLogic Server (WLS) is taking long time to rollback transaction after customers application is initiating transaction for rollback.
And after marking the "transaction for rollback", SQL is executed for that same transaction without a transaction marked for rollback failure.
We observe the following peculiar behavior in the stack :
1.) Firstly we see the transaction being marked for roll back at 4:25:02 PM:
In the above stack trace, we see that transaction manager takes 21 seconds to rollback this transaction and why SQL queries are executed for the same transaction ID if that was marked rollback.
The application executed many SQL statements using this transaction without any errors, this is unexpected from customer perspective as they expect transactions marked for rollback to be essentially in an error/inactive state and any attempt to execute further SQL within that transaction should fail with a "transaction marked for rollback" type of error/exception.
Instead the transaction allowed the SQL to be executed and remained apparently active for 21 seconds and only then did it throw a RollbackException due to the transaction being marked for rollback.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms