Newly created Outbound Connection Pool for DB Adapter shows in WebLogic Console but composites encounter BINDING.JCA-12510 error as not available on SOA managed server at runtime

(Doc ID 1297725.1)

Last updated on NOVEMBER 17, 2016

Applies to:

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


You are developing a simple composite application which you will execute on Fusion Middleware 11g Release 1. The composite leverages a BPEL component and Database Adapter, to invoke a very simple SQL query and return the response back to the invoker.

You have used the WebLogic console to complete the required WebLogic Server configuration by having created an Outbound Connection Pool on the Database Adapter and the DataSource that it references. You have also invoked an UPDATE to propagate the changes from the resulting deployment plan and everything looks as expected from the WebLogic server console.

However, you have since deployed and tested a composite that uses the DbAdapter and accesses the newly defined Outbound Connection Pool but at runtime the composite is failing with the following JCA Binding error:

Exception occurred when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'DBSelect_sysdate' failed due to:
JCA Binding Component connection issue.
JCA Binding Component is unable to create an outbound JCA (CCI) connection.
DBAdapter_Test_DBTestImpl:DBSelect_sysdate [ DBSelect_sysdate_ptt::DBSelect_sysdate(DBSelect_sysdateInput_msg,DBSelect_sysdateOutputCollection) ]:
The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510
JCA Resource Adapter location error.
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:
The reason for this is most likely that either
1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or
2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/DB/TestOutboundConnection.
In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR).
Please correct this and then restart the Application Server

The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.


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