Exceptions Due to Duplicate Root Context of JNDI Name in JMS module (Doc ID 1390490.1)

Last updated on MAY 24, 2017

Applies to:

Oracle Weblogic Server - Version 10.3.5 and later
Information in this document applies to any platform.

Symptoms

This document describes the JNDI naming conventions in JMS Module. Same name in the JNDI root context throws errors during creating resources in the JMS Module.

Test Case:
<Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1324412121328' for task 'weblogic.deploy.configChangeTask.8'. Error is: 'weblogic.application.ModuleException: Error preparing connection factory JMSModule!Queue12345CF'
weblogic.application.ModuleException: Error preparing connection factory JMSModule!Queue12345CF
at weblogic.jms.module.JMSModule.prepareUpdate(JMSModule.java:618)
at weblogic.jms.module.ModuleCoordinator.prepareUpdate(ModuleCoordinator.java:487)
at weblogic.application.internal.flow.DeploymentCallbackFlow$5.next(DeploymentCallbackFlow.java:644)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepareUpdate(DeploymentCallbackFlow.java:410)
Truncated. see log file for complete stacktrace
Caused By: javax.naming.CannotProceedException; remaining name 'CF'
at javax.naming.spi.ContinuationContext.getTargetContext(ContinuationContext.java:43)
at javax.naming.spi.NamingManager.getContinuationContext(NamingManager.java:770)
at weblogic.jndi.internal.BasicNamingNode.getContinuationCtx(BasicNamingNode.java:1180)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:216)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
Truncated. see log file for complete stacktrace>
 

Cause

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