Transactions to MQ through Foreign JMS in a SOA cluster fail with the exception "XAER_RMFAIL : Resource manager is unavailable" (Doc ID 2047408.1)

Last updated on AUGUST 09, 2017

Applies to:

Oracle SOA Suite - Version 11.1.1.6.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.1.1.1.0 version, Technology Adapters

When a JMS Adapter is connected to MQ in a clustered SOA Domain (more than one SOA Managed server), transactions are failing with the following error in the logs:

ERROR
-----------------------
start() failed on resource 'eis/resource/Queue': XAER_RMFAIL : Resource manager is unavailable
javax.transaction.xa.XAException: Internal error: XAResource 'eis/resource/Queue' is unavailable
at weblogic.transaction.internal.XAResourceDescriptor.checkResource(XAResourceDescriptor.java:951)
at weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResourceDescriptor.java:634)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1246)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1180)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:285)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:561)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:488)
at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:118)
at weblogic.connector.outbound.ConnectionHandlerBaseImpl.prepareHandle(ConnectionHandlerBaseImpl.java:709)
at weblogic.connector.outbound.ConnectionHandlerBaseImpl.createConnectionHandle(ConnectionHandlerBaseImpl.java:376)
at weblogic.connector.outbound.ConnectionInfo.createConnectionHandle(ConnectionInfo.java:431)
at weblogic.connector.outbound.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:321)
at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:129)
at oracle.tip.adapter.jms.JmsConnectionFactory.getConnection(JmsConnectionFactory.java:93)
at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAConnectionManager$JCAConnectionPool.createJCAConnectionFactory(JCAConnectionManager.java:1404)
at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAConnectionManager$JCAConnectionPool.newPoolObject(JCAConnectionManager.java:1285)
at oracle.integration.platform.blocks.adapter.fw.common.ObjectPool.checkOut(ObjectPool.java:215)
at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAConnectionManager$JCAConnectionPool.checkOut(JCAConnectionManager.java:1507)
at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAConnectionManager.obtainJCAConnection(JCAConnectionManager.java:736)
at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.executeJcaInteraction(JCAInteractionInvoker.java:180)
at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.invokeJcaReference(JCAInteractionInvoker.java:551)
at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.invokeAsyncJcaReference(JCAInteractionInvoker.java:511)
at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAEndpointInteraction.performAsynchronousInteraction(JCAEndpointInteraction.java:547)
at oracle.integration.platform.blocks.adapter.AdapterReference.post(AdapterReference.java:256)
at oracle.integration.platform.blocks.mesh.AsynchronousMessageHandler.doPost(AsynchronousMessageHandler.java:142)



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