Monday, 20 January 2014

JCA Binding execute of Reference operation 'insert' failed due to: 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/DB/Sample from JNDI and get a new Connection Handle.”

HI Folks ,

I have experienced this issue in my clients environment.


There is a disconnection between WLS and JCA connection pool manager.
When we update JCA adapter deployment with new JNDI and redeploy the adapter instance then WLS invalidates all the existing connections and it seems WLS even doesn't know that JCA connection pool is the owner of these connections and it doesn't inform JCA pool manager that it has invalidated the connections.
Now JCA pool manager has no idea of what happened and it still maintains invalid connections in its pool.

When client requests JCA connection then JCA manager try to return the dead connection which results above error.

 Solution 1

1.Try applying patch 11812911 

 Solution 2

2.This solution is about just updating weblogic-ra.xml without redeploying it

•   Update adapter JNDI from the weblogic administration console deployments
•   Save the changes
•   Go to the Deployments page
•   Check the required Adapter
•   Click on the Update button
•   Choose "Update this application in place with new deployment plan changes. (We need to specify a deployment plan for this option) Do not choose the default option: "Redeploy this application using the following deployment files"

•   Click finish 

Happy Learning...!!!!!!!!   Fun Sharing........!!!!!!!!!!!!!

No comments:

Post a Comment