JCAPS 6.3: Error In Transaction Handling, When the Connection To the JMS Server Is Broken (Doc ID 1556677.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle Java CAPS Enterprise Service Bus - Version R6.3 and later
Information in this document applies to any platform.
*** Checked for Relevance on 09-Feb-2016 ***

Symptoms

Error in transaction handling when the connection to the JMS server is broken.

When the connection to the JMS server is broken (error in com.stc.jms.client.STCXAResource.start), the created transaction is not closed correctly. When this occurs, subsequent JMS calls generate the following exception/Error:


ERROR
-----------------------
javax.transaction.xa.XAException: Cannot call start() unless previous XID is committed or rolled back

2012-12-11T14:04:25.505+0100 / mark ###1
A JMS transaction is created. Creation fails because of java.io.EOFException (connection to JMS-server (stcms.exe) is broken.
Transaction ID: xid:4871251:3A060000D2DED9896465776565656169617031312C7365727665722C503131303637:6465776565656169617031312C7365727665722C5031313036372C09
----------------------------------------------------------------------------------------------------------------
2012-12-11T14:04:25.554+0100 / mark ###2
Container tries to prepare transaction created above. Leads to javax.transaction.xa.XAException: No end for this transaction.
----------------------------------------------------------------------------------------------------------------
2012-12-11T14:04:25.957+0100 / mark ###3
Later JMS calls result in a javax.transaction.xa.XAException: Cannot call start() unless previous XID is committed or rolled back exception because the transaction created in ###1 is not closed correctly.

All subsequent JMS-calls fail with the same error message.

Cause

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