5 Replies Latest reply on Nov 22, 2004 2:16 AM by Vaicar George

    No beans in the JNDI view

    Vaicar George Newbie

      Hi everybody,

      I have this problem with JBoss 3.2.1 running on jdk 1.4.2.03.
      I use ant to compile&deploy one war file and a jar file under server/default/deploy.
      The two files ejb-jar.xml and jboss.xml are in the correct place under META-INF directory in my jar file.

      The problem is : when I start the server, I can't see on the console that my EJB's contained in the jar file are being deployed on the server.
      Also I started the Jboss management console, but there is none of my EJBs in the JNDI view or the beans page.

      On the client I load the jndi.properties file, but when I lookup an EJB I get an NameNotFoundException, which is normal, because the beans are not deployed.

      Please help me on this topic - why my beans are not being deployed on server?

      Thanks for helping,
      George

        • 1. Re: No beans in the JNDI view
          Darran Lofthouse Master

          Are you sure that your jar file is being put into the correct deploy folder?

          • 2. Re: No beans in the JNDI view
            Vaicar George Newbie

            hi darran,

            I'm sure my jar is under JBOSS_HOME/server/default/deploy.

            Also, I have another .war file that is also there, and its context is being created ok, and it can be accesed.

            It only seems to be a problem with the jar file.I checked the server log and I can't see any error.

            Thank you for giving any thoughts,
            George

            • 3. Re: No beans in the JNDI view
              Bernd Zeitler Expert

              Read the server.log even if there are no errors in it.
              Is you jar being picked up by a deployer? Which deploy is serving your jar? Really no errors in the log during deployment? Then the directory used is not a watched by your server. Did you change the configuration of the deployers (located in conf/jboss-service.xml)?
              You probably want to configure log4j using the TRACE level for package org.jboss.deployment (an example is within conf/log4j.xml).
              I bet, JBoss (out of the box) will pick up every jar in the deploy directory when the sever starts. In fact, JBoss tries to deploy everything, believe me ;-)

              • 4. Re: No beans in the JNDI view
                Vaicar George Newbie

                When the servers starts and tries to deploy my .jar (ejb-angest.jar), there is the following error:

                ERROR [URLDeploymentScanner] MBeanException: Exception in MBean ope
                ration 'checkIncompleteDeployments()'
                Cause: Incomplete Deployment listing:
                Packages waiting for a deployer:
                [org.jboss.deployment.DeploymentInfo@73f3e926 { url=file:/C:/jboss-3.2.1/server/
                default/deploy/ejb-angest.jar }
                deployer: null
                status: null
                state: INIT_WAITING_DEPLOYER
                watch: file:/C:/jboss-3.2.1/server/default/deploy/ejb-angest.jar
                lastDeployed: 1100940983418
                lastModified: 1100940983378
                mbeans:
                ]Incompletely deployed packages:
                [org.jboss.deployment.DeploymentInfo@73f3e926 { url=file:/C:/jboss-3.2.1/server/
                default/deploy/ejb-angest.jar }
                deployer: null
                status: null
                state: INIT_WAITING_DEPLOYER
                watch: file:/C:/jboss-3.2.1/server/default/deploy/ejb-angest.jar
                lastDeployed: 1100940983418
                lastModified: 1100940983378

                It is not a problem with the EJB deployer, because it is configured ok in jboss-service.xml, and other jar I have from another project it is getting deployed ok on the same server configuration.

                Please, any ideea would be helpful
                Thank you,
                George

                • 5. Re: No beans in the JNDI view
                  Vaicar George Newbie

                  I found out what was the problem;
                  The ejb-jar.xml and jboss.xml files inside my jar had the .XML extension (with uppercase).

                  Sorry for bothering