After Database Restart Connections in the Pool Return Error: "SQLException: No More Data to Read from Socket"
(Doc ID 400349.1)
Last updated on JUNE 03, 2024
Applies to:
Oracle Containers for J2EE - Version 10.1.2.1.0 and laterInformation in this document applies to any platform.
Symptoms
When a database is restarted, AS 10.1.2 connections in the datasource's pool return an error to the applications, and the connection is kept in the pool,
so every attempt from applications to connect to the database keeps aborting with errors.
The error reported could be one of the following:
java.sql.SQLException: No more data to read from socket
java.sql.SQLException: OALL8 is in an inconsistent state.
java.sql.SQLException: Io exception: Broken pipe
Changes
The issue documented here occurred during an application migration from AS 9.0.3.1 to AS 10.1.2.
The AS 9.0.3 application worked OK after a restart of the Database.
So this note documents how to handle this scenario in AS 10.1.2. Nevertheless, the solution here is more generic and it can also apply when working with non-oracle databases.
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 |