JDBC/UCP Ignores Oracle.net.CONNECT_TIMEOUT Value
(Doc ID 2747070.1)
Last updated on FEBRUARY 27, 2025
Applies to:
Universal Connection Pool - Version 19.3 and laterInformation in this document applies to any platform.
Symptoms
UCP 19.3 is used for connection to Oracle 12c database. When doing:
the value of oracle.net.CONNECT_TIMEOUT is set in the properties correctly, but it is not used when connecting to the database.
It is observed that when not setting loginTimeout (pds.setLoginTimeout()), the above property value will be overwritten by default loginTimeout of 0, in in the initConnectionFactory method of PoolDataSourceImpl class.
Also, if loginTimeout is set, the value should be seconds (pds.setLoginTimeout(3) // for 3 seconds). This value is used, but it does not convert correctly to milliseconds, so it times out in 3ms.
Changes
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 |