Stop/Start of AQ Adapter causes OSB Proxy to fail with [Connector:199176]Unable to execute allocateConnection(...) on ConnectionManager. A stale Connection Factory or Connection Handle may be used.
(Doc ID 2597286.1)
Last updated on APRIL 01, 2024
Applies to:
SOA Suite Cloud Service - Version N/A and laterInformation in this document applies to any platform.
Symptoms
After using WebLogic Console to Stop the AQ Adapter, and then start it again today, inbound OSB Proxies no longer poll AQ.
The error in the logfiles is:
[2019-10-08T09:58:52.617-05:00] [XXXXX_server_1] [ERROR] [] [oracle.soa.adapter.aq.inbound] [tid: JCA-work-instance:AQ Adapter-2] [userId: <WLS Kernel>] [ecid: 1235ae7a-f39c-4094-80e9-7f0ab3ea8f60-03f672b7,0] [partition-name: DOMAIN] [tenant-name: GLOBAL] [endpoint_name: TESTPROJECT/ProxyServices/TESTPROXY_PS] DBDequeueAgent_recover: [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 perform another lookup of the Connection Factory eis/AQ/AQConnection from JNDI and get a new Connection Handle.[[ 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 perform another lookup of the Connection Factory eis/AQ/AQConnection from JNDI and get a new Connection Handle.
at
weblogic.connector.outbound.ConnectionManagerImpl.checkIfPoolIsValid(ConnectionManagerImpl.java:479)
at
weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:115)
at
oracle.tip.adapter.aq.v2.jca.AQConnectionFactory.getConnection(AQConnectionFactory.java:83)
at
oracle.tip.adapter.aq.v2.database.AbstractDequeueAgent.recoverConnection(AbstractDequeueAgent.java:311)
at
oracle.tip.adapter.aq.v2.database.AbstractDequeueAgent.recover(AbstractDequeueAgent.java:276)
at
oracle.tip.adapter.aq.v2.database.AbstractDequeueAgent.runInbound(AbstractDequeueAgent.java:129)
at
oracle.tip.adapter.aq.v2.database.AbstractDequeueAgent.run(AbstractDequeueAgent.java:106)
at
weblogic.connector.outbound.ConnectionManagerImpl.checkIfPoolIsValid(ConnectionManagerImpl.java:479)
at
weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:115)
at
oracle.tip.adapter.aq.v2.jca.AQConnectionFactory.getConnection(AQConnectionFactory.java:83)
at
oracle.tip.adapter.aq.v2.database.AbstractDequeueAgent.recoverConnection(AbstractDequeueAgent.java:311)
at
oracle.tip.adapter.aq.v2.database.AbstractDequeueAgent.recover(AbstractDequeueAgent.java:276)
at
oracle.tip.adapter.aq.v2.database.AbstractDequeueAgent.runInbound(AbstractDequeueAgent.java:129)
at
oracle.tip.adapter.aq.v2.database.AbstractDequeueAgent.run(AbstractDequeueAgent.java:106)
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 |
Cause |
Solution |
References |