Java Stored Procedure Ignores Timeout Period Specified For Socket Connection On 11.2.0.2 Database On Windows
(Doc ID 1335414.1)
Last updated on AUGUST 09, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.2 to 11.2.0.2 [Release 11.2]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Microsoft Windows x64 (64-bit) - Version: 2008 R2
Symptoms
A java stored procedure ignores the timeout period set on a socket and times
out after the default TCP timeout setting on the operating system. The
problem reproduces only on 11.2.0.2 database on Windows platform. If a
Timeout of 4 seconds is used in the following code, this will not be honoured
and the socket will timeout only after 21 seconds (default tcp timeout on
Windows 2008).
The problem does not reproduce on Linux. Also a standalone java program
works fine on both Linux and Windows.
Changes
Upgrade from database 11.2.0.1 to 11.2.0.2
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 |