How WLContext.CONNECT_TIMEOUT and RESPONSE_READ_TIMEOUT Work In Terms of Configured Timeout Values

(Doc ID 2406830.1)

Last updated on JUNE 12, 2018

Applies to:

Oracle WebLogic Server - Version 12.1.3.0.0 and later
Information in this document applies to any platform.

Goal

Need to get a bit more information about how the WLContext.CONNECT_TIMEOUT and WLContext.RESPONSE_READ_TIMEOUT work. Specifically, if we are doing some testing in which we make a call across a firewall where we don’t have a rule in place to allow the connection (in order to force a connection timeout). Right now, if we are setting the WLContext.CONNECT_TIMEOUT to for example, 5 seconds but we can see that it takes a good bit longer for the call to timeout. 
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms