Although weblogic.datasource.endLocalTxOnNonXAConWithCommit is True, a Non-XA Connection is Not Committed After Closing the Connection
Last updated on NOVEMBER 05, 2016
Applies to:Oracle WebLogic Server - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 12c]
Information in this document applies to any platform.
From WebLogic (WLS) 12.1.2, weblogic.datasource.endLocalTxOnNonXAConWithCommit is added as system property.
If application does not complete (commit or rollback) the local transaction before closing the non-XA connection, it expects that the connection will be committed when the property is true (default value is true).
Oracle® Fusion Middleware Administering JDBC Data Sources for Oracle WebLogic Server
Chapter 9 - JDBC Data Source Transaction Options
Local Transaction Completion when Closing a Connection
However, if a non-XA connection has been used in global transaction once, the connection is not committed after closing connection without commit/rollback.
Therefore, if the application does not call commit or rollback explicitly for the connection, it remains non-resolved transaction or the connection will be committed/rolled back on the unexpected timing.
In summary, this issue occurs under the following conditions:
- weblogic.datasource.endLocalTxOnNonXAConWithCommit is true (default is true).
- setAutoCommit is false.
- Application does not complete (commit/rollback) the local transaction before closing the non-XA connection.
- The Non-XA connection has been used in global transaction before used in local transaction. (It means that it has been used as JTSConnection).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms