My Oracle Support Banner

Number of Threads Waiting for a Database Connection Increases, Calls to SOA Services Show Timeout Errors and no more BPEL Instances are Created (Doc ID 799601.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle(R) BPEL Process Manager - Version 10.1.3.4 to 10.1.3.5.0
Information in this document applies to any platform.
JDBC version 10.1.0.5, 10.2.0.3, 10.2.0.4

Checked for relevance on 08-03-2012
***Checked for relevance on 09-August-2013***

Symptoms


When using SOA Suite Services like Applications Adapters and Database Adapters, after some running time all services stop and the application that make calls to these SOA services start to show timeout error.When checking the BPEL console, you can observed that no instance is generated.

Using AS Control you can observe that in the metrics of connection pool "Threads waiting connections" values are increasing and no more new connection is possible.

Checking the data-sources.xml file we can see that the connection pools define for several of these connections have the following attributes defined:

<connection-pool name="test" abandoned-connection-timeout="180" inactivity-timeout="50" max-connections="50">
....
</connection-pool>

Restarting the SOA Suite solves the issue.

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

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