My Oracle Support Banner

Data Source XaTransactionTimeout Value was Applied But not be Logged Correctly in Debug Log Message (Doc ID 2521858.1)

Last updated on OCTOBER 09, 2023

Applies to:

Oracle WebLogic Server - Version 12.1.2.0.0 to 12.2.1.3.0 [Release 12c]
Information in this document applies to any platform.

Symptoms

The XaTransactionTimeout is the number of seconds to set as the transaction branch timeout.

If set, this value is passed as the transaction timeout value in the XAResource.setTransactionTimeout() call on the XA resource manager, typically the JDBC driver.

When this value is set to 0, the WebLogic Server Transaction Manager passes the global WebLogic Server transaction timeout in seconds in the method.

If set, this value should be greater than or equal to the global WebLogic Server transaction timeout.

Note: You must enable XaSetTransactionTimeout to enable setting the transaction branch timeout.

But the following JTAXA debug message is not correctly as expected to show JTA timeout even if the JBCXAParamsBean.XaSetTransactionTimeout is true and global JTA timeout is 30 seconds, DBCXAParamsBean.XaTransactionTimeout is 60 seconds.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.