How WLContext.CONNECT_TIMEOUT and RESPONSE_READ_TIMEOUT Work in Terms of Configured Timeout Values
(Doc ID 2406830.1)
Last updated on OCTOBER 08, 2018
Applies to:Oracle WebLogic Server - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Need to get a bit more information about how the WLContext.CONNECT_TIMEOUT and WLContext.RESPONSE_READ_TIMEOUT work. Specifically, if testing is done when a call is made across a firewall where there is no rule in place to allow the connection (in order to force a connection timeout). Right now, if setting the WLContext.CONNECT_TIMEOUT to, for example, 5 seconds but it takes a good bit longer for the call to timeout.
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