My Oracle Support Banner

Error: The Method 'commit' Cannot be Called when a Global Transaction is Active Displayed in log.xml (Doc ID 824419.1)

Last updated on MARCH 07, 2019

Applies to:

Oracle Enterprise Service Bus - Version 10.1.3.3 and later
Information in this document applies to any platform.
***Checked for relevance on 04-Apr-2011***


Symptoms

Environment:
Clustered SOA Suite 10.1.3.3 installation including AIA Telco PIP 2.0.1

Problem:

All ESB processes when executed, the following error is visible in the log file and the ESB Console does not display the message instance:

 

<MESSAGE>
<HEADER>
<TSTZ_ORIGINATING>2009-02-03T16:15:45.490+03:00</TSTZ_ORIGINATING>
<COMPONENT_ID>j2ee</COMPONENT_ID>
<MSG_ID>J2EE DS-00262</MSG_ID>
<MSG_TYPE TYPE="WARNING"></MSG_TYPE>
<MSG_LEVEL>1</MSG_LEVEL>
<HOST_ID></HOST_ID>
<HOST_NWADDR><IPADDRESS></HOST_NWADDR>
<MODULE_ID>datasource</MODULE_ID>
<THREAD_ID>24</THREAD_ID>
<USER_ID>XXXX</USER_ID>
</HEADER>
<CORRELATION_DATA>
<EXEC_CONTEXT_ID><UNIQUE_ID><UNIQID></UNIQUE_ID><SE
Q>0</SEQ></EXEC_CONTEXT_ID>
</CORRELATION_DATA>
<PAYLOAD>
<MSG_TEXT>The method 'commit' cant be called when a global transaction is
active.</MSG_TEXT>
</PAYLOAD>
</MESSAGE>

 

 

Steps to reproduce the problem:

1. Restart the SOA Suite and make sure message instances tracking in turned on in ESB Control at http://<hostname>:<port>/esb.
2. Execute ESB flow.
3. Review log.xml which displays: The method 'commit' cant be called when a global transaction is active.
4. Review ESB Control and the message instance is not shown.

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.