javax.naming.NameNotFoundException: DLQ not bound

hpe.com | 4 months ago
  1. Speed up your debug routine!

    Automated exception search integrated into your IDE

    6 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

      DLQ not bound

      at org.jnp.server.NamingServer.getBinding()
    2. org.jnp.server
      NamingServer.lookup
      1. org.jnp.server.NamingServer.getBinding(NamingServer.java:581)
      2. org.jnp.server.NamingServer.getBinding(NamingServer.java:589)
      3. org.jnp.server.NamingServer.getObject(NamingServer.java:595)
      4. org.jnp.server.NamingServer.lookup(NamingServer.java:342)
      5. org.jnp.server.NamingServer.lookup(NamingServer.java:316)
      5 frames
    3. org.jnp.interfaces
      NamingContext.lookup
      1. org.jnp.interfaces.NamingContext.lookup(NamingContext.java:667)
      2. org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
      2 frames
    4. Java RT
      InitialContext.lookup
      1. javax.naming.InitialContext.lookup(InitialContext.java:392)
      1 frame
    5. JBoss Common Classes
      Util.lookup
      1. org.jboss.util.naming.Util.lookup(Util.java:215)
      1 frame