My Oracle Support Banner

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

Last updated on DECEMBER 11, 2017

Applies to:

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


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(
at weblogic.jms.module.ModuleCoordinator.prepareUpdate(
at weblogic.application.internal.flow.DeploymentCallbackFlow$
at weblogic.application.utils.StateMachineDriver.nextState(
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepareUpdate(
Truncated. see log file for complete stacktrace
Caused By: javax.naming.CannotProceedException; remaining name 'CF'
at javax.naming.spi.ContinuationContext.getTargetContext(
at javax.naming.spi.NamingManager.getContinuationContext(
at weblogic.jndi.internal.BasicNamingNode.getContinuationCtx(
at weblogic.jndi.internal.BasicNamingNode.lookup(
at weblogic.jndi.internal.BasicNamingNode.lookup(
Truncated. see log file for complete stacktrace>


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

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