High JNDI Lookup Timeouts When Servers are down During Disaster Recovery
(Doc ID 2928866.1)
Last updated on FEBRUARY 17, 2023
Applies to:Oracle WebLogic Server - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
There is a WebLogic Server (WLS) application that creates the initialContext every time it invoke a remote EJB. The problem occurs when some servers are down for Disaster Recovery (DR) test. Some requests remain blocked in
weblogic.jndi.requestTimeout parameters were setup, but in any case the response times for JNDI lookups are high when servers are stopped for DR.
Following things were tried but did not help:
1) Defining the cluster address in the DNS didn't help to reduce the response time in JNDI lookup
2) Also setting the "weblogic.jndi.forceResolveDNSName=true" didn't help to reduce the response time in JNDI lookup
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