"BINDING.JCA-12561 JCA Resource Adapter location error" DB Adapter Invoke Fails with Unable to Locate the JCA Resource Adapter Error (Doc ID 1360817.1)

Last updated on JUNE 07, 2017

Applies to:

OracleAS Adapters - Version 10.1.3.1 and later
Oracle Service Bus - Version 10.3.1 to 11.1.1.5.0 [Release AS10gR3 to 11g]
Information in this document applies to any platform.
***Checked for relevance on 28-Feb-2013***

Symptoms

In OSB cluster domain with domain spread across multiple physical machines, when DBAdapter is invoked on managed server (which is located in different machine than where admin server is located), results the below error.


Exception:
<Sep 13, 2011 10:40:01 AM EDT> <Error> <JCA_FRAMEWORK_AND_ADAPTER> <BEA-000000> <servicebus:/WSDL/Common/Adapter/GetUserDataDbAdapter [ GetUserDataDbAdapter_ptt::GetUserDataDbAdapter(InputParameters,OutputParameters) ] - Could not invoke operation 'GetUserDataDbAdapter' due to:

BINDING.JCA-12511
JCA Binding Component connection issue.
JCA Binding Component is unable to create an outbound JCA (CCI) connection.
servicebus:/WSDL/Common/Adapter/GetUserDataDbAdapter [ GetUserDataDbAdapter_ptt::GetUserDataDbAdapter(InputParameters,OutputParameters) ] - : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12561
JCA Resource Adapter location error (WebLogic).
Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/>
The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/DB/CCDB'.
The reason for this is most likely that either
1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic J2EE Application server or
2) the JNDI <jndi-name> setting in the WebLogic JCA deployment descriptor has not been set to eis/DB/CCDB. In the last case you might have to add a new 'connector-factory' entry (connection) to the deployment descriptor.
Please correct this and then restart the WebLogic Application Server

Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections.

at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFPort_JCA$JCAConnectionPool.createJCAConnectionFactory(WSIFPort_JCA.java:1624)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFPort_JCA$JCAConnectionPool.newPoolObject(WSIFPort_JCA.java:1486)
at oracle.tip.adapter.sa.impl.fw.common.ObjectPool.checkOut(ObjectPool.java:174)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFPort_JCA$JCAConnectionPool.checkOut(WSIFPort_JCA.java:1695)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFPort_JCA.obtainJCAConnection(WSIFPort_JCA.java:1015)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:394)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeOperation(WSIFOperation_JCA.java:353)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:312)
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.invokeWsifProvider(JCABindingReferenceImpl.java:350)
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:253)
at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:598)
...........
Caused by: BINDING.JCA-12561
JCA Resource Adapter location error (WebLogic).
Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/>
The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/DB/CCDB'.
The reason for this is most likely that either
1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic J2EE Application server or
2) the JNDI <jndi-name> setting in the WebLogic JCA deployment descriptor has not been set to eis/DB/CCDB. In the last case you might have to add a new 'connector-factory' entry (connection) to the deployment descriptor.
Please correct this and then restart the WebLogic Application Server

at oracle.tip.adapter.fw.AdapterFrameworkException.createJndiLookupException(AdapterFrameworkException.java:151)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFPort_JCA$JCAConnectionPool.createJCAConnectionFactory(WSIFPort_JCA.java:1573)
... 69 more
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'eis.DB.CCDB'. Resolved 'eis.DB'; remaining name 'CCDB'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
............

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