My Oracle Support Banner

Too Many SO_TIMEOUT And Inactive Database Sessions After Upgrading to WebLogic 12.2.1.4 (Doc ID 2814178.1)

Last updated on JUNE 19, 2024

Applies to:

Oracle WebLogic Server - Version 12.2.1.4.0 and later
Information in this document applies to any platform.

Goal

After upgrading to WebLogic 12.2.1.4, you are experiencing many SO_TIMEOUT and inactive database sessions in your production environment.

For this bug there appears to be a patch.  Oracle.jdbc.ReadTimeout Prevents Proper Query Timeout Handling, Causing Connection Leak <Note 2561983.1> states:

Cause
Read timeout in JDBC 12.2.0.0.0 and later prevents proper query timeout handling
Bug 29788820 - READTIMEOUT PREVENTS PROPER QUERY TIMEOUT HANDLING, CAUSING CONNECTION LEAK

Solution
Apply <Patch 29788820>


<Patch 29788820> is already installed  but it doesn’t seem to have any effect.

Is it possible to determine why the Patch 29788820 has no effect?
 

Solution

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