Last updated on AUGUST 03, 2016
Applies to:JDBC - Version 10.1.0.5 and later
Information in this document applies to any platform.
***Checked for relevance on 29-Mar-2013***
There is a requirement to set a timeout on Socket level for the jdbc thin driver. This was done by specifying oracle.net.READ_TIMEOUT, but this is not working anymore in JDBC 11.1 or higher.
prop.put ("user", "user_name");
prop.put ("password", "write_password");
prop.put ("oracle.net.READ_TIMEOUT", "180000"); // timeout in ms
conn = DriverManager.getConnection (url, prop);
upgrade of jdbc driver to 11.1 or higher
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms