My Oracle Support Banner

E1 : JAS : DB: Inactive JDBC Connections Not Getting Cleared as per connectionTimeout and cleanPoolInterval Defined in jdbj.ini (Doc ID 2498782.1)

Last updated on FEBRUARY 13, 2019

Applies to:

JD Edwards EnterpriseOne Tools - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

JDBC connections created from the JAS server to the database server and are cleared based on two setting in the jdbj.ini - connectionTimeout and cleanPoolInterval 

For example 

cleanPoolInterval=300000 (5 minutes)
connectionTimeout=30 (30 minutes)


cleanPoolInterval is the amount of time in milliseconds that the pool cleaner is set to clean data sources that have a validation string.  When cleaning occurs, any connections which have been flagged as idle will be cleaned up.  The amount of time between a connection becoming idle and being cleaned up can be as long as the connectionTimeout value plus the cleanPoolInterval value.

However it is noticed from the database side that there are INACTIVE sessions in the database for a far longer duration ( greater than connectionTimeout value plus the cleanPoolInterval value.)
The connections are cleared from the JAS session , connections are only left open from the database side

These inactive sessions are causing performance issues in the database. 

 

Changes

 

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
Changes
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.