SOA 11g: SOADatasource Connection Leak Count is >0 when InactiveConnectionTimeout is Enabled for Datasource

(Doc ID 1558387.1)

Last updated on SEPTEMBER 18, 2017

Applies to:

Oracle SOA Platform - Version and later
Information in this document applies to any platform.


On : version, BPEL Service Engine

In a SOA Suite domain, if InactiveConnectionTimeout is set for system datasources (for eg. SOADatasource), over time, the datasource shows a growing Leaked connection Count in the Datasource monitoring screen.

Leaked count should always be 0.

The issue can be reproduced at will with the following steps:
1. Set the InactiveConnectionTimeout to lesser value (less than a normal transaction run in BPEL). For eg. Inactive connection timeout is set to 30 seconds whereas BPEL will sometimes run above 30 seconds to finish its transaction. 


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms