InactiveConnectionTimeout Creates a lot of Sessions below MinPoolSize
Last updated on MARCH 08, 2017
Applies to:Universal Connection Pool - Version 188.8.131.52.0 to 184.108.40.206.0
Information in this document applies to any platform.
A UCP pool that has been active and then goes idle may experience a large amount of connections continually closed and new connections opened.
As per the current behavior in UCP 111.0.7 and UCP 220.127.116.11 connections that are found to be inactive as per the InactiveConnectionTimeout property will be closed. On the other hand, once the pool has reached the MinPoolSize due to prior activity, the UCP will open new connections to maintain the minimum number of connections.
This situation can cause an unnecessary amount of open and close session activity even though the UCP pool is idle and will reflect in a database audit of session events
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