2 Replies Latest reply on Dec 4, 2009 2:08 AM by jaikiran pai

    javax.naming.NameNotFoundException: QName_ejb_vehicle not bo

    Richard Opalka Master

      Hi Folks,

      I'd like to ask experts first to don't waste my time. How could I fix this problem?


        • 1. Re: javax.naming.NameNotFoundException: QName_ejb_vehicle no
          jaikiran pai Master

          I don't have the details of those tests, so i am not sure what exactly might be going on. But looking at the stacktrace, it appears to be an application client which appears to be doing a JNDI lookup and running into a NameNotFoundException. Looking the ENC of that application client:

          +- UserTransaction[link -> UserTransaction] (class: javax.naming.LinkRef)
          +- metaData (class: org.jboss.metadata.client.jboss.JBossClientMetaData)
          +- env (class: org.jnp.interfaces.NamingContext)
          | +- ejb (class: org.jnp.interfaces.NamingContext)
          | | +- EJBVehicle[link -> SOAPFaultException_ejb_vehicle] (class: javax.naming.LinkRef)
          +- classPathEntries (class: java.util.ArrayList)
          

          I think the right jndi name to use would be java:comp/env/ejb/EJBVehicle in the lookup.
          A bit weird part in that exception stacktrace is, it probably isn't reporting the jndi name which is leading to this exception. For example, i see this in the stacktrace:

          javax.naming.NameNotFoundException: SOAPFaultException_ejb_vehicle not bound

          and also this:

          javax.naming.NameNotFoundException: QName_ejb_vehicle not bound


          It would be weird if the code is really looking up "SOAPFaultException_ejb_vehicle" or "QName_ejb_vehicle".

          As a side note, you probably would want to see this http://www.jboss.org/community/wiki/HowtouseanapplicationclientinJBoss-5, just in case it's a configuration issue.


          • 2. Re: javax.naming.NameNotFoundException: QName_ejb_vehicle no
            jaikiran pai Master

             

            "jaikiran" wrote:

            | | +- EJBVehicle[link -> SOAPFaultException_ejb_vehicle] (class: javax.naming.LinkRef)
            
            

            A bit weird part in that exception stacktrace is, it probably isn't reporting the jndi name which is leading to this exception. For example, i see this in the stacktrace:

            javax.naming.NameNotFoundException: SOAPFaultException_ejb_vehicle not bound




            After paying a bit more attention at the JNDI contents, shows that the EJBVehicle jndi name is "linking" to SOAPFaultException_ejb_vehicle (and hence that's the name being reported in the NameNotFoundException). So apparently, it's the "linking" of the ENC jndi name to the global jndi name which isn't happening correct.