How to Use Timeouts for Closing OC4J Managed Datasource JDBC Connections? (Doc ID 1126046.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle Containers for J2EE - Version: 10.1.3.0.0 and later   [Release: AS10gR3 and later ]
Information in this document applies to any platform.

Goal

***Checked for relevance on 15-Feb-2012***

Many applications are observed with JDBC connections that do not close. These connections do not close and have a lot of busy resources. They can only be freed by rebooting the OC4J J2EE data source's connection_pool, but this isn't the supposed solution.

Is there any timeout setting that can close these connections in a maximum time of e.g. 24 hours?

Solution

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