WebLogic Server JTA Timeout Values
(Doc ID 786431.1)
Last updated on JUNE 04, 2019
Applies to:Oracle WebLogic Server - Version 8.1 to 18.104.22.168.0
Oracle Communications Order and Service Management - Version 2.5.2 to 22.214.171.124.0 [Release 2.5 to 7.3.0]
Information in this document applies to any platform.
Reviewed relevance Jan 15, 2014
Reviewed relevance July 6, 2016
Reviewed relevance Nov 08, 2017
Reviewed relevance April 09, 2019
Quite often the Java Transaction API (JTA) is set to the default timeout value for many OSM development and/or testing installations. The default value is 30 seconds and when there are bottlenecks in the system, many OSM java transactions cannot finish within 30 seconds. As a result, the user will see errors such as the following:
java.sql.SQLException: Transaction BEA1-04341F727880E4C0F083 not active anymore. tx status = Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 32 seconds
at com.mslv.oms.dataaccesslayer.a.getConnection(Unknown Source)
at com.mslv.oms.dataaccesslayer.a.execute(Unknown Source)
Truncated. see log file for complete stacktrace
Ideally, the root cause of the bottleneck should be identified and resolved accordingly. However sometimes it is necessary to increase the JTA value, for example:
a) the nature of transaction will take longer than 30 seconds
b) it takes time to fix system bottleneck and a quick fix is needed.
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