JNDI Connection Error in SOA Suite 12C (Could not create/access the TopLink Session)

Issue –> While testing the composite I got the below error.

Error –> <bpelFault><faultType>0</faultType><bindingFault xmlns=”http://schemas.oracle.com/bpel/extension“><part name=”summary”><summary>Exception occured when binding was invoked. Exception occured during invocation of JCA binding: “JCA Binding execute of Reference operation ‘merge’ failed due to: Could not create/access the TopLink Session. This session is used to connect to the datastore. Caused by Exception [EclipseLink-7060] (Eclipse Persistence Services – 2.3.1.v20111018-r10243): org.eclipse.persistence.exceptions.ValidationException Exception Description: Cannot acquire data source [jdbc/TEST_DB]. Internal Exception: javax.naming.NameNotFoundException: Unable to resolve ‘jdbc.TEST_DB’. Resolved ‘jdbc’; remaining name ‘TEST_DB’. You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server. This exception is considered not retriable, likely due to a modelling mistake. “. The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary></part><part name=”detail”><detail> Exception Description: Cannot acquire data source [jdbc/TEST_DB]. Internal Exception: javax.naming.NameNotFoundException: Unable to resolve ‘jdbc.TEST_DB. Resolved ‘jdbc’; remaining name ‘TEST_DB'</detail></part><part name=”code”><code>null</code></part></bindingFault></bpelFault>

Solution –>To Resolve these errors please follow the below steps.

1. Check if the outbound connection pool is created with correct data source jndi name or not.  Check the Connection pool XAdatasource name is updated with your datasource jndi name, if not update it and update your DB adapter.

2. Check if the data source is targeted to your soa server or not, if not target it.