My Oracle Support Banner

Weblogic Console Hangs and Times Out after Adding a Nested JNDI Name (Doc ID 1275499.1)

Last updated on SEPTEMBER 11, 2020

Applies to:

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

Symptoms

When using WebLogic Server (WLS) 10.3.3 in Production Mode, an attempt is made to create a JNDI entry which is a concatenation of two character strings separated by '.' such as 'a.b'.

If 'a' already exists in the JNDI tree when the resource with JNDI name 'a.b' is targeted at a Managed Server, this causes an Admin Console hang.

Eventually the console times out with the following error displayed in the Admin Console:

The hang could occur whenever an attempt is made to target such a concatenated JNDI name at a resource.

Here is a specific example to reproduce the issue:

  1. Start the Admin Server, and then start (any) managed server from the WLS Admin Console.
  2. Take the domain lock for update.
  3. Navigate to Services -> Messaging -> JMS Modules.
  4. Click 'New', enter any value for 'name' and 'descriptor file name'. Leave the 'location in domain' entry blank and click 'Next.'
  5. Target the JMS Module at the managed server and click 'Next.'
  6. Tick the check box labeled 'Would you like to add resources to the JMS system module?' and click 'Finish.'
  7. Click 'New,' select Connection Factory, and click 'Next.'
  8. Enter any unique value for 'name', and then choose a JNDI name, for example, 'a'.
  9. Click 'Next.' The next screen should have the managed server checked by default.
  10. Click 'Finish' and activate the changes.
  11. Take the lock for update again, and repeat steps 3 - 10. On step 8, ensure that the new JNDI name includes a substring of the old JNDI name
  12. When an attempt is made to activate the second change, the Admin Console hangs.

It is possible to use the console to perform other tasks, for example to stop the managed server, but any attempt to activate or rollback the changes results in an error.

This prevents effective administration of the WLS configuration. The managed server needs to be restarted before normal operations can resume.

Cause

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
Symptoms
Cause
Solution


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