javax.naming.NameNotFoundException: 'mybindname'; remaining name 'mybindname'

Oracle Community | 3004 | 2 decades 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

    RMI Objects running on single cluster memb. only avail on that

    Oracle Community | 2 decades ago | 3004
    javax.naming.NameNotFoundException: 'mybindname'; remaining name 'mybindname'

    Root Cause Analysis

    1. javax.naming.NameNotFoundException

      'mybindname'; remaining name 'mybindname'

      at weblogic.rmi.extensions.BasicRequest.sendReceive()
    2. weblogic.rmi.extensions
      BasicRequest.sendReceive
      1. weblogic.rmi.extensions.BasicRequest.sendReceive(BasicRequest.java:44)
      1 frame
    3. weblogic.jndi
      WLContext_WLStub.lookup
      1. weblogic.jndi.WLContext_WLStub.lookup(WLContext_WLStub.java:192)
      1 frame
    4. weblogic.jndi.toolkit
      WLContextStub.lookup
      1. weblogic.jndi.toolkit.WLContextStub.lookup(WLContextStub.java:545)
      1 frame
    5. mypackage
      MyClass.lookup
      1. mypackage.MyClass.lookup(...)
      1 frame