5 Replies Latest reply on Mar 9, 2005 4:24 PM by Scott Stark

    EJB not bound

    bigy Newbie

      We are converting from jboss-3.0.0 here at work to jboss-4.0.1. As we are moving the applications one by one over for testing, I have found an issue with an EJB based java app. I am getting a EJB not bound. Is there a new jboss.xml file format? What am I missing? Here's the jboss.xml file...any/all help is much appreciated.

      <?xml version="1.0" encoding="UTF-8"?>
      <!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 3.0//EN" "http://www.jboss.org/j2ee/dtd/jboss_3_0.dtd">
       To add beans that you have deployment descriptor info for, add
       a file to your XDoclet merge directory called jboss-beans.xml that contains
       the <session></session>, <entity></entity> and <message-driven></message-driven>
       markup for those beans.

        • 1. Re: EJB not bound
          bigy Newbie

          Here is the full error:

          javax.naming.NameNotFoundException: ejb not bound

          • 2. Re: EJB not bound
            Darran Lofthouse Master

            Have you checked the console for any deployment errors?

            Also have you had a look at JNDI view to see what is actually bound?

            • 3. Re: EJB not bound
              luc lamontagne Newbie

              I've a similar problem. I tried to migrate from Websphere to JBoss 4.0.1 and I've convert my ibm-ejb-jar.xmi in jboss.xml.

              I've a ejb-jar.xml like that


              <resource-ref id="ResourceRef_1080661309044">




              and a jboss.xml like that




              this two file is in the META-INF directory

              the problem is want I start my server I've this error:

              org.jboss.deployment.DeploymentException: Error in jboss.xml for Bean DateLogique: found in jboss.xml but not in ejb-jar.xml

              the EJB is in ejb-jar.xml and in jboss.xml with the same name.

              Somebody have a idea?

              • 4. Re: EJB not bound
                John Le Guen Newbie

                I am getting a similar problem, but in a migration from 3.2.6 - 3.2.7. I have an application that had local and remote interfaces for Stateless session beans. They are configured in ejb-jar.xml with then name "ejb/EJBProcessUser". With earlier versions 3.2.3-3.2.6 The java application looks up using the name "local/ejb/EJBProcessUser" from the env context. It works if I deploy to 3.2.6 but the same ear fails EJB not bound. A look at the JNDI names using the jmx-console shows that the bean is bound.

                John Le Guen

                • 5. Re: EJB not bound
                  Scott Stark Master


                  [JBAS-275] - 2 identical named mdbs cannot deploy