0 Replies Latest reply on Aug 10, 2016 12:00 PM by snigdhaamaraneni1

    Spawn of thread loosing its jndi lookup context - jboss AS 6

    snigdhaamaraneni1

      Recently we migrated from jboss-5 to jboss AS 6.1.0.final, we call a third party web service. after getting the response back when we are trying to do a jndi  lookup of the ejb we get the following exception

       

      Root:

      javax.naming.NameNotFoundException: env not bound

        at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)

        at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)

        at org.jnp.server.NamingServer.getObject(NamingServer.java:785)

        at org.jnp.server.NamingServer.lookup(NamingServer.java:396)

        at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:728)

        at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:835)

        at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:688)

        at javax.naming.InitialContext.lookup(InitialContext.java:411)

       

       

      From my analysis so far, from the main thread we are passing an asynchandler to a third party web service and the response is received in a child thread. In that child thread it is trying to lookup for an ejb but the context is lost within the child, it is unable to pass this to the main thread.

      The same thing is working in jboss 5.1.0.GA with the same java version 7

       

      Any solution on this would be helpful

      Thanks in Advance