Long running queries are forced to rollback or release a connection when Inactive Connection Timeout is reached. (Doc ID 2087333.1)

Last updated on AUGUST 01, 2017

Applies to:

Oracle WebLogic Server - Version 10.3.5 to 12.1.3.0.0
Information in this document applies to any platform.

Symptoms

InactiveConnectionTimeoutSeconds (Inactive Connection Timeout) is defined as the number of inactive seconds on a reserved connection before WebLogic Server reclaims the connection and releases it back into the connection pool.

Link : http://docs.oracle.com/cd/E24329_01/web.1211/e24367/ds_tuning.htm#JDBCA194

When you have a long running SQL query (say this query takes 90 seconds to complete) which exceeds the Inactive Connection Timeout value (say 20 seconds) specified in the JDBC Data source, the inactive timeout cleanup thread forcibly closes this connection after the Inactive Connection Timeout is reached with a BEA-001153 error code. (even before the application calls a commit).

 

Below is the code snippet from application :

 

 

Cause

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