javax.naming.NameNotFoundException: 'mybindname'; remaining name > 'mybindname' > at > weblogic.rmi.extensions.BasicRequest.sendReceive(BasicRequest.java:44) > at > weblogic.jndi.WLContext_WLStub.lookup(WLContext_WLStub.java:192) > at > weblogic.jndi.toolkit.WLContextStub.lookup(WLContextStub.java:545) >

Oracle Community | 3004 | 2 decades ago
  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' > at > weblogic.rmi.extensions.BasicRequest.sendReceive(BasicRequest.java:44) > at > weblogic.jndi.WLContext_WLStub.lookup(WLContext_WLStub.java:192) > at > weblogic.jndi.toolkit.WLContextStub.lookup(WLContextStub.java:545) >
  2. 0
    samebug tip
    Make sure you use the same name for your database everywhere in context.xml.
  3. 0
    samebug tip
    Add localDataSource="true" to the realm when using local database.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0
    samebug tip
    Try removing the server.xml file and adding it again to the project, and do a Clean Build.

    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

      'mybindname'; remaining name > 'mybindname' > at > weblogic.rmi.extensions.BasicRequest.sendReceive(BasicRequest.java:44) > at > weblogic.jndi.WLContext_WLStub.lookup(WLContext_WLStub.java:192) > at > weblogic.jndi.toolkit.WLContextStub.lookup(WLContextStub.java:545) >

      at mypackage.MyClass.lookup()
    2. mypackage
      MyClass.lookup
      1. mypackage.MyClass.lookup(...)
      1 frame