Configuring AQ-JMS Adapter for XA Returns Error ORABPEL-12141 ERRJMS_CONN_FAC_NOT_FOUND (Doc ID 966101.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle Enterprise Service Bus - Version 10.1.3.4 to 10.1.3.4 [Release AS10gR3]
Oracle(R) BPEL Process Manager 10g - Version 10.1.3.4 to 10.1.3.4 [Release AS10gR3]
Information in this document applies to any platform.
***Checked for relevance on 12-Dec-2011***


Symptoms

You have configured your SOA system for XA operation following this document:
Oracle SOA Suite 10g XA and
RAC Database Configuration Guide
An Oracle White Paper
May 2009
Oracle SOA Suite XA and RAC Database Configuration Guide (PDF)
You have also configured the transaction logfiles to use file based persistence (as specified by the Oracle SOA Suite 10g XA and RAC Database Configuration Guide) by modifying this file: 
$ORACLE_HOME/j2ee/<ESB Runtime/BPEL containername>/config/transaction-manager.xml
In the BPEL and/or ESB service you are using a XA configured AQ-JMS adapter.
When there are transaction logfiles existing in the specified transaction-manager.xml directory the following error is seen when the system is started:
09/10/30 00:24:40 LEVEL-0: JMSConnectionFactoryFactory_getConnectionFactory: 
Will now try to determine if the 'ConnectionFactoryLocation' 
java:comp/resource/aqjmstest/XAQueueConnectionFactories/myQCF is a loadable 
Java class. If so, the above exception can be ignored. 
09/10/30 00:24:40 LEVEL-0: Error while creating managed connection: 
09/10/30 00:24:40 ORABPEL-12141 
ERRJMS_CONN_FAC_NOT_FOUND. 
Unable to instantiate connection factory. JMS adapter was unable to look up 
the connection factor 
java:comp/resource/aqjmsOut/XAQueueConnectionFactories/myQCF neither through 
JNDI nor instantiate it as a Java class 
Please examine the log file to determine the problem. 

09/10/30 00:24:40 at 
oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JM 
SConnectionFactoryFactory.java:207) 
09/10/30 00:24:40 at 
oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getQueueConnectionFacto 
ry(JMSConnectionFactoryFactory.java:98) 
09/10/30 00:24:40 at 
oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:192) 
09/10/30 00:24:40 at 
oracle.tip.adapter.jms.JMS.JMSConnection.<init>(JMSConnection.java:133) 
09/10/30 00:24:40 at 
oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManaged 
ConnectionFactory.java:428) 
09/10/30 00:24:40 at 
oracle.tip.adapter.jms.JmsManagedConnectionFactory.createDefaultConnection(Jms 
ManagedConnectionFactory.java:419) 
09/10/30 00:24:40 at 
oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManaged 
ConnectionFactory.java:382) 
09/10/30 00:24:40 at 
oracle.tip.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(Jms 
ManagedConnectionFactory.java:106) 
09/10/30 00:24:40 at 
com.evermind.server.connector.ApplicationConnectionManager.createManagedConnec 
tion(ApplicationConnectionManager.java:1398) 
09/10/30 00:24:40 at 
oracle.j2ee.connector.ConnectionPoolImpl.createManagedConnectionFromFactory(Co 
nnectionPoolImpl.java:327) 
09/10/30 00:24:40 at 
oracle.j2ee.connector.ConnectionPoolImpl.access$800(ConnectionPoolImpl.java:98 
) 
09/10/30 00:24:40 at 
oracle.j2ee.connector.ConnectionPoolImpl$NonePoolingScheme.getManagedConnectio 
n(ConnectionPoolImpl.java:1211) 
09/10/30 00:24:40 at 
oracle.j2ee.connector.ConnectionPoolImpl.getManagedConnection(ConnectionPoolIm 
pl.java:785) 
09/10/30 00:24:40 at 
com.evermind.server.connector.JCAResourceManagerFactory.connect(JCAResourceMan 
agerFactory.java:119) 
09/10/30 00:24:40 at 
oracle.as.j2ee.transaction.tpc.recovery.RecoveryManagerPresumedAbort.getNewXAR 
esource(RecoveryManagerPresumedAbort.java:834) 
09/10/30 00:24:40 at 
oracle.as.j2ee.transaction.tpc.recovery.RecoveryManagerPresumedAbort.acquireXA 
Resource(RecoveryManagerPresumedAbort.java:779) 
09/10/30 00:24:40 at 
oracle.as.j2ee.transaction.tpc.recovery.RecoveryManagerPresumedAbort.acquireXA 
Resource(RecoveryManagerPresumedAbort.java:729) 
09/10/30 00:24:40 at 
com.evermind.server.ApplicationServerTransactionManager.createRecoveryManager( 
ApplicationServerTransactionManager.java:1200) 
09/10/30 00:24:40 at 
com.evermind.server.ApplicationServer.initializeDefaultApplication(Application 
Server.java:1612) 
09/10/30 00:24:40 at 
com.evermind.server.ApplicationServer.initializeAutoDeployedApplications(Appli 
cationServer.java:1586) 
09/10/30 00:24:40 at 
com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:1018) 
09/10/30 00:24:40 at 
com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.ja 
va:131) 
09/10/30 00:24:40 at java.lang.Thread.run(Thread.java:619) 
09/10/30 00:24:40 Caused by: javax.naming.NamingException: Not in an 
application scope - start OC4J with the -userThreads switch if using 
user-created threads 
09/10/30 00:24:40 at 
com.evermind.server.PreemptiveApplicationContext.getContext(PreemptiveApplicat 
ionContext.java:30) 
09/10/30 00:24:40 at 
com.evermind.naming.FilterContext.lookup(FilterContext.java:126) 
09/10/30 00:24:40 at 
com.evermind.server.PreemptiveApplicationContext.lookup(PreemptiveApplicationC 
ontext.java:42) 
09/10/30 00:24:40 at 
javax.naming.InitialContext.lookup(InitialContext.java:392) 
09/10/30 00:24:40 at 
oracle.tip.adapter.jms.JMS.JMSFactory.jndiLookup(JMSFactory.java:227) 
09/10/30 00:24:40 at 
oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JM 
SConnectionFactoryFactory.java:138) 
09/10/30 00:24:40 ... 22 more 
09/10/30 00:25:42 log4j:WARN No appenders could be found for logger (wsif). 
09/10/30 00:25:42 log4j:WARN Please initialize the log4j system properly. 
09/10/30 00:25:43 LEVEL-0: JMSConnectionFactoryFactory_getConnectionFactory: 
looking up 'java:comp/resource/aqjmsOut/XAQueueConnectionFactories/myQCF' 
09/10/30 00:25:43 LEVEL-0: JMSConnectionFactoryFactory_getConnectionFactory: 
JNDI Naming exception when looking up 
java:comp/resource/aqjmsOut/XAQueueConnectionFactories/myQCF: Not in an 
application scope - start OC4J with the -userThreads switch if using 
user-created threads 

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