The First Instance Using The Redeployed Adapter Fails with BINDING.JCA-12511 and " Unable to execute allocateConnection(...) on ConnectionManagers"
(Doc ID 1341107.1)
Last updated on NOVEMBER 13, 2023
Applies to:
Oracle SOA Suite - Version 11.1.1.3.0 and laterInformation in this document applies to any platform.
Symptoms
The first instance executed after redeploying an outbound/inbound adapter component fails with the following error:
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:NNNNN]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:NNNNN]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)
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |