My Oracle Support Banner

RIB Adapters are Shutting Down with "XAER_RMFAIL : Resource manager is unavailable" Errors (Doc ID 1929839.1)

Last updated on JUNE 01, 2020

Applies to:

Oracle Retail Integration Bus - Version 13.2.4 to 14.1.3 [Release 13.2 to 14.1]
Oracle SOA Suite - Version 11.1.1.7.0 to 11.1.1.7.0 [Release 11gR1]
Information in this document applies to any platform.

Symptoms

Occasionally RIB adapters fail with below errors. Once errors begin to occur it might span to other message family adapters and resulting them to shutdown. The only way to recover from this is to restart the rib-app instance or bounce the complete RIB WebLogic domain. 

Errors:

"javax.ejb.EJBException: Unexpected exception in com.retek.rib.app.getnext.impl.GetNextPublisherEjb.getNextAndPublishMessages:
com.retek.rib.binding.exception.PublishException: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XAER_RMFAIL start() failed on resource 'rib-app-managed-datasource_xyz': XAER_RMFAIL : Resource manager is unavailable
oracle.jdbc.xa.OracleXAException
at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1110)
at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:240)
at weblogic.jdbc.jta.DataSource.start(DataSource.java:790)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1247)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1180)
....
Caused by: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XAER_RMFAIL start() failed on resource 'rib-app-managed-datasource_xyz': XAER_RMFAIL : Resource manager is unavailable
oracle.jdbc.xa.OracleXAException
.....
ERROR com.retek.rib.j2ee.AbstractTimerAdapterTask - Stopped adapter(<PUBLISH ADAPTER>) through jmx call"

Here are some observations during this issue:

  1. It was observed that connection pools are getting exhausted and the relevant rib-app application is not able to get new connections.
  2. This issue is mostly occurred during RIB peak load and/or while processing large messages.
  3. Sometimes the messages are treated as poisonous even though valid and written to the RIB logs directory as *.xml.

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.