Weblogic Console Hangs and Times Out after Adding a Nested JNDI Name
Last updated on SEPTEMBER 06, 2016
Applies to:Oracle Weblogic Server - Version: 10.3.3
Information in this document applies to any platform.
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:
An error occurred during activation of changes, please see the log for details.
DeploymentService:290053]Request with id '1,292,587,532,802' timed out on admin server
The following error is written to the AdminServer.log:
<Failures were detected while initiating activate task for application 'SystemModule-1'.>
####<Dec 17, 2010 1:05:32 PM GMT> <Warning> <Deployer> <myhost.oracle.com> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <
> <> <> <1292591132854> <BEA-149078> <Stack trace for message 149004
java.lang.Exception: [DeploymentService:290053]Request with id '1,292,587,532,802' timed out on admin server.
AdminServer> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1292591132884> <BEA-240003> <Console encountered the following error java.lang.Exception: [DeploymentService:290053]Request with id '1,292,587,532,802' timed out on admin server.
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:
- Start the Admin Server, and then start (any) managed server from the WLS Admin Console.
- Take the domain lock for update.
- Navigate to Services -> Messaging -> JMS Modules.
- Click 'New', enter any value for 'name' and 'descriptor file name'. Leave the 'location in domain' entry blank and click 'Next.'
- Target the JMS Module at the managed server and click 'Next.'
- Tick the check box labeled 'Would you like to add resources to the JMS system module?' and click 'Finish.'
- Click 'New,' select Connection Factory, and click 'Next.'
- Enter any unique value for 'name', and then choose a JNDI name, for example, 'a'.
- Click 'Next.' The next screen should have the managed server checked by default.
- Click 'Finish' and activate the changes.
- 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, e.g., 'a.b'
- 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.
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