WebLogic Server JMS Data Source Frequently Fails with BEA-010213 javax.transaction.xa.XAException (Doc ID 1484996.1)

Last updated on AUGUST 17, 2023

Applies to:

Symptoms

This issue occurred in a WebLogic domain with an Admin server and three managed servers all residing on same physical machine. Over a period of several weeks, one of the managed servers threw the following data source exceptions, and the transactions were rolled back. A whole server restart was required to restore the services.

The JDBC data source cannot be configured for transactions, but will support the Java Transaction API (JTA) with Java Messaging System (JMS). See "Handling JMS Transactions with JDBC Stores".

Also, see "Creating a JDBC Store" where it states:

Note: You cannot specify a JDBC data source that is configured to support global (XA) transactions. Therefore, the specified JDBC data source must use a non-XA JDBC driver. In addition, you cannot enable Logging Last Resource or Emulate Two-Phase Commit in the data source. This limitation does not remove the XA capabilities of layered subsystems that use JDBC stores. For example, WebLogic JMS is fully XA-capable regardless of whether it uses a file store or any JDBC store.

Cause

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