"Socket read timed out" Error Trying to Connect from JDBC Application
(Doc ID 2051087.1)
Last updated on MAY 21, 2020
Applies to:JDBC - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 11.2 to 12.1]
Universal Connection Pool - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 11.2 to 12.1]
Oracle WebLogic Server - Version 10.3.6 to 10.3.6
Information in this document applies to any platform.
JDBC database connections using a driver earlier than 18.104.22.168 fail with a "Socket read timed out" error, such as the one listed in the following exception stack:
org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is java.sql.SQLException: Exception occurred while getting connection: oracle.ucp.UniversalConnectionPoolException: Cannot get Connection from Datasource: java.sql.SQLRecoverableException: IO Error: Socket read timed out
With a limited number of JDBC connections (such as a single, small JDBC or UCP connection pool), the application works successfully.
With a high number of JDBC connections, the "IO Error: Socket read timed out" error occurs.
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