SOA 11g: BINDING.JCA-12511 Error after Configuration Change to JCA Adapter (Doc ID 1460899.1)

Last updated on NOVEMBER 03, 2016

Applies to:

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

Symptoms

You are using a JCA Adapter. You use this adapter already in your SOA Composite. To replicate the problem execute below steps:

1) Send a request through the adapter. You will see a correct result.

2) Make an update in configuration of connection pool of the JCA_Adapter (i.e maxConnectionPool from 20 to 30)

3) Send a second request, and you will see that the request will fail

4) Send some more requests. They all will complete successfully

So the issue is with the first request that fails after changing the configuration, with below error messages:

 

BINDING.JCA-12511
JCA Binding Component connection issue.
JCA Binding Component is unable to create an outbound JCA (CCI) connection.

The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: javax.resource.spi.IllegalStateException: [Connector:199176]Unable to execute allocateConnection(...) on ConnectionManager. A stale Connection Factory or Connection Handle may be used. The connection pool associated with it has already been destroyed. Try to re-lookup Connection Factory eis/BRM from JNDI and get a new Connection Handle.
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.
..


javax.resource.spi.IllegalStateException: [Connector:199176]Unable to execute allocateConnection(...) on ConnectionManager. A stale Connection Factory or Connection Handle may be used. The connection pool associated with it has already been destroyed. Try to re-lookup Connection Factory eis/BRM from JNDI and get a new Connection Handle.
at weblogic.connector.outbound.ConnectionManagerImpl.checkIfPoolIsValid(ConnectionManagerImpl.java:442)


Patch for Bug 11812911 does not resolve this issue.

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