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.

  • Cluster start up exception WLS 6.1 sp2
    via by 3004,
  • Startup problems for managed server
    via by 3004,
  • problem in clustering ejb
    via by 3004,
    • javax.naming.NameNotFoundException: Unable to resolve >> weblogic.transaction.resources.servera. Resolved: >> 'weblogic.transaction.resour >> ces' Unresolved:'servera' ; remaining name '' >> at >> weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingN >> ode.java:887) >> at >> weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:219) >> at >> weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:129 >> ) >> at >> weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:558) >> at >> weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562) >> at >> weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562) >> at >> weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562) >> at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown >> Source) >> at >> weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298) >> at >> weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java >> :93) >> at >> weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267) >> at >> weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:166) >> 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.java >> :262) >> at >> weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java >> :229) >> at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
    No Bugmate found.