javax.naming.NameNotFoundException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • Startup problems for managed server
    via by 3004,
  • Cluster start up exception WLS 6.1 sp2
    via by 3004,
  • problem in clustering ejb
    via by 3004,
    • javax.naming.NameNotFoundException: Unable to resolve > >weblogic.transaction.resources.CCOMServer01. Resolved: > >'weblogic.transaction.resources' Unresolved:'CCOMServer01' ; remaining > >name > >'' > > at > >weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNaming N > >ode.java:802) > > at > >weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:209) > > at > >weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:12 9 > >) > > at > >weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:496) > > at > >weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:500) > > at > >weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:500) > > at > >weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:500) > > at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown > >Source) > > at > >weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288) > > at > >weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.jav a > >:93) > > at > >weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:257) > > at > >weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:158) > > at > >weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92) > > at > >weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112) > > at > >weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.jav a > >:253) > > at > >weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.jav a > >:220) > > at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
    No Bugmate found.