Weblogic Transaction Cannot Begin if JTA Timeout is Set to the Maximum int Value 2147483647
(Doc ID 1585026.1)
Last updated on SEPTEMBER 11, 2020
Applies to:Oracle WebLogic Server - Version 10.3.4 to 10.3.6
Information in this document applies to any platform.
The following exception may be seen when the JTA transaction timeout is set close to the maximum unsigned int value of (2^31 -1) = 2147483647:
The issue occurs when using JTA and JTA timeout is set as described within Weblogic Server Online help at: Domain -> Services -> JTA -> click "More Info..." at "Timeout Seconds" configuration. The problem here is that the maximum int value is treated as a negative int in opposition to the WebLogic documentation and standard signed int arithmetic.
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