OSB DB Polling Service Error: "The Connection Pool Associated With It Has Already Been Destroyed"
(Doc ID 2183838.1)
Last updated on AUGUST 12, 2024
Applies to:
Oracle Service Bus - Version 12.1.3.0.0 and laterInformation in this document applies to any platform.
Symptoms
After deploying an OSB service using a DB Adapter the following error is seen in the logs:
[2016-07-20T20:27:52.323-07:00] [osb_server1] [NOTIFICATION] [] [oracle.soa.adapter.db.inbound] [tid: JCA-work-instance:Database Adapter-25] [userId: ] [ecid: caaf68e4-ffaa-4833-852d-ae01a2858e30-00000007,0] [APP: Service Bus JCA Transport Provider] [service_name: testDBAdapterPoll/dbPollService] BINDING.JCA-11624[[
DBActivationSpec Polling Exception.
Query name: [dbPollServiceSelect], Descriptor name: [dbPollService]. Polling the database for events failed on this iteration.
Caused by 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/DB/EBS from JNDI and get a new Connection Handle..
This exception is considered not retriable, likely due to a modelling mistake. This polling process will shut down, unless the fault is related to processing a particular row, in which case polling will continue but the row will be rejected (faulted).
DBActivationSpec Polling Exception.
Query name: [dbPollServiceSelect], Descriptor name: [dbPollService]. Polling the database for events failed on this iteration.
Caused by 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/DB/EBS from JNDI and get a new Connection Handle..
This exception is considered not retriable, likely due to a modelling mistake. This polling process will shut down, unless the fault is related to processing a particular row, in which case polling will continue but the row will be rejected (faulted).
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 |