High JNDI Lookup Timeouts When Servers are down During Disaster Recovery (Doc ID 2928866.1)

Last updated on FEBRUARY 20, 2024

Applies to:

Goal

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

 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.