javax.naming.NameNotFoundException: Unable to resolve 'EmployeeDetails' >Resolved >: '' Unresolved:'EmployeeDetails' ; remaining name 'EmployeeDetails' at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundR >equest.java:109) at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteR >ef.java:262) at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteR >ef.java:229) at weblogic.jndi.internal.ServerNamingNode_WLStub.lookup(Unknown >Source) >

Oracle Community | 3004 | 1 decade ago
tip
Click on the to mark the solution that helps you, Samebug will learn from it.
As a community member, you’ll be rewarded for you help.
  1. 0

    looking up bean deployed in clustered server.

    Oracle Community | 1 decade ago | 3004
    javax.naming.NameNotFoundException: Unable to resolve 'EmployeeDetails' >Resolved >: '' Unresolved:'EmployeeDetails' ; remaining name 'EmployeeDetails' at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundR >equest.java:109) at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteR >ef.java:262) at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteR >ef.java:229) at weblogic.jndi.internal.ServerNamingNode_WLStub.lookup(Unknown >Source) >
  2. 0

    Java mon amour: June 2012

    javamonamour.org | 2 years ago
    javax.naming.NameNotFoundException: While trying to lookup 'soa-infra:comp.ApplicationContext' didn't find subcontext 'soa-infra:comp'. Resolved ''; remaining name 'soa-infra:comp/ApplicationContext'
  3. Speed up your debug routine!

    Automated exception search integrated into your IDE

  4. 0

    Jdeveloper and weblogic

    Stack Overflow | 1 year ago | Kareem Mohamed
    oracle.jbo.DMLException: JBO-29114 ADFContext is not setup to process messages for this exception. Use the exception stack trace and error code to investigate the root cause of this exception. Root cause error code is JBO-27200. Error message parameters are {0=Data Source, 1=java:comp/env/jdbc/testArchiveDS}
  5. 0

    Weblogic JMS Server throwing "weblogic.wsee.DefaultQueue" not found error.

    Oracle Community | 7 years ago | 768834
    javax.naming.NameNotFoundException: Unable to resolve 'weblogic.wsee.DefaultQueue'. Resolved 'weblogic.wsee'; remaining name 'DefaultQueue'

    20 unregistered visitors
    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. javax.naming.NameNotFoundException

      Unable to resolve 'EmployeeDetails' >Resolved >: '' Unresolved:'EmployeeDetails' ; remaining name 'EmployeeDetails' at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundR >equest.java:109) at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteR >ef.java:262) at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteR >ef.java:229) at weblogic.jndi.internal.ServerNamingNode_WLStub.lookup(Unknown >Source) >

      at weblogic.jndi.internal.WLContextImpl.lookup()
    2. weblogic.jndi.internal
      WLContextImpl.lookup
      1. weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:338)
      2. weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:333)
      2 frames
    3. Java RT
      InitialContext.lookup
      1. javax.naming.InitialContext.lookup(InitialContext.java:350)
      1 frame
    4. Unknown
      EjbTestClient.main
      1. EjbTestClient.<init>(EjbTestClient.java:35)
      2. EjbTestClient.main(EjbTestClient.java:72)
      2 frames