Last updated on SEPTEMBER 02, 2015
Applies to:Oracle WebLogic Server - Version 9.0 to 10.3.3
Information in this document applies to any platform.
I have an application that does JNDI lookup on a remote server. If that server is down, the Context.lookup call is not timing out.
I try setting the following -D parameters and restarting the instance, but it appears that Context does not honor the TCP/IP timeout values. The -D parameters added to the server startup script are as follows:
None of the above parameters helped.
The question is how to set a timeout value for an initialContext.lookup() call so that it will time out if the remote server doesn't respond within a specified period of time?
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