javax.naming.NameAlreadyBoundException: generate-unique-jms-client-id Is Not set In the JMS Data Descriptor (Doc ID 1321057.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle Weblogic Server - Version: 10.3.1 and later   [Release: and later ]
Information in this document applies to any platform.

Symptoms

One instance of a WebLogic Server (WLS) cluster fails to start while creating a durable subscriber during the activation of a JMS module.

Here is the complete stack trace of the relevant error:

javax.naming.NameAlreadyBoundException: The JNDI name weblogic.jms.internal.subscription.cid_DeclarationsFilenetBridgeMDB_sid_DeclarationsFilenetBridgeMDB was found, and was bound to an object of type weblogic.jms.common.DurableSubscription : DurableSubscription((SingularAggregatable(<3898676013644124700.1>:0)) STIR-BTW!JMSstirZvatp021@WorkFlow.Output.Topic:null:false)
 at weblogic.jms.backend.BEConsumerImpl.registerDurableSubscription(BEConsumerImpl.java:886)
 at weblogic.jms.backend.BEConsumerImpl.init(BEConsumerImpl.java:329)
 at weblogic.jms.backend.BEConsumerImpl.<init>(BEConsumerImpl.java:276)
 at weblogic.jms.backend.BETopicImpl.recoverDurableSubscription(BETopicImpl.java:438)
 at weblogic.jms.backend.BEDurableSubscriptionStore.restoreSubscriptions(BEDurableSubscriptionStore.java:166)
 at weblogic.jms.backend.BETopicRuntimeDelegate.activate(BETopicRuntimeDelegate.java:94)
 at weblogic.jms.backend.udd.UDDEntity.activate(UDDEntity.java:307)
 at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
 at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
 at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
 at weblogic.jms.module.JMSModule.activate(JMSModule.java:332)
 at weblogic.jms.module.ModuleCoordinator.activate(ModuleCoordinator.java:194)
 at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
 at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:411)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:74)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:66)
 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:629)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:206)
 at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:40)
 at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
 at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
 at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
 at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:42)
 at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
 at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
 at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
 at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
 at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
 at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
 at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89) at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

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