Managed Server Does Not Start After Adding This Managed Server to an Existing Domain (Doc ID 1274476.1)

Last updated on SEPTEMBER 09, 2017

Applies to:

Symptoms

After adding a new server to a cluster of a SOA domain, the following message is seen in the added server:

<Nov 8, 2010 5:42:08 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: MessageDispatcherBean is unable to connect to the JMS destination: OraSDPM/Queues/OraSDPMWSRcvQ1. The Error was:
javax.naming.NameNotFoundException: While trying to lookup 'OraSDPM.Queues.OraSDPMWSRcvQ1' didn't find subcontext 'Queues'. Resolved 'OraSDPM'; remaining name 'Queues/OraSDPMWSRcvQ1'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.jms.common.CDS$2.run(CDS.java:222)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:216)

Cause

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