My Oracle Support Banner

ESB Connection Pool Exhaustion (Doc ID 1328449.1)

Last updated on DECEMBER 09, 2019

Applies to:

Oracle Enterprise Service Bus - Version and later
Information in this document applies to any platform.


There is a database connection exhaustion issue.
Observed that the OTB PIP had created over 2000 connections to it's dehydration store database, this caused the database to run out of resources, and then subsequently bounced the OTB PIP. At that time there was no max connection limit on the ESB Pool connection setting in the data-sources.xml file.
For connection pool parameters to limit the maximum number of connections for the ESB, had set it to 300 connection. Discovered that in less than 15 hours, the ESB connection pool has hit the limit on this connection number, this caused the OTB PIP to be unresponsive. A subsequent restart clear the issue.
However, this raises an important issue, we need to determine what is ramping up the connection count (and not releasing or re-using connections) to the dehydration store.

We see this type of errors in our soasuite logs.

11/05/31 15:22:15 file:///app/soa/bpel/domains/default/tmp/.bpel_SyncCustomerPartyListBRMCommsProvABCSImpl_1.0_be4e8b3d4e5670350eeddb4cdfd8e236.tmp/Xform_PCM_OP_CUST_COMMIT_CUSTOMER_to_SyncCustomerPartyListResponseEBM.xsl<Line 174, Column 236>: XML-22044: (Error) Extension function error: Error invoking 'populateXRefRow':'java.lang.RuntimeException: org.apache.slide.common.ServiceAccessException: Service access error : Unable to get a physical connection from the database...there are no connections available.'


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.