8 Replies Latest reply on Dec 1, 2009 10:52 AM by Wolfgang Knauf

    ear not deployed in JBoss start up with derby database

    akhil achuthan Newbie

      hello

      I am trying to start my jboss(5.1) with derby, but my ear does not get deployed at all...

      Jboss gives an impression that it has started, when i look in inside my ear is not noticed by jboss at all......

      The same setup works fine with oracle and mysql, with my ear properly deployed....

      Any help???

      the below is the contents of my datastore xml:


      <local-tx-datasource>
      <jndi-name>DefaultDS</jndi-name>
      <connection-url>jdbc:derby:MY_DATABASE;create=true</connection-url>
      <driver-class>org.apache.derby.jdbc.EmbeddedDriver</driver-class>
      <user-name>NA</user-name>
      NA
      <!-- <check-valid-connection-sql>show tables</check-valid-connection-sql>-->
      <track-statements>true</track-statements>
      <max-pool-size>40</max-pool-size>
      <blocking-timeout-millis>30000</blocking-timeout-millis>
      <exception-sorter-class-name>com.temp.nms.server.genlib.database.dberror.DataBaseErrorChecker</exception-sorter-class-name>
      <!-- Don't change the isolation level, this will affect schedulers-->
      <!--<transaction-isolation>TRANSACTION_READ_UNCOMMITTED</transaction-isolation>-->
      <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->

      <type-mapping>Derby</type-mapping>


      I have derby.jar and derbyclient.jar placed in my lib folder....

        • 1. Re: ear not deployed in JBoss start up with derby database
          jaikiran pai Master

           

          "akhilachuthan" wrote:


          Jboss gives an impression that it has started, when i look in inside my ear is not noticed by jboss at all......



          Please explain what that means.

          • 2. Re: ear not deployed in JBoss start up with derby database
            akhil achuthan Newbie

            Im using a notification framework to check whether jboss is started successfully or not... This shows jboss as started after the a few seconds....

            But the ear that put inside the deploy folder is not deployed with jboss. A couple of exceptions that i see in the log on the way of server startup are given below....

            org.jboss.deployers.spi.DeploymentException: Error deploying: file:/D:/WORKSPACES/05_oct_09/dnms/output/DNMS/EMS/server/ems/conf/bootstrap/vfs.xml
            at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
            at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:136)
            at org.jboss.system.server.profileservice.ProfileServiceBootstrap.initBootstrapMDs(ProfileServiceBootstrap.java:433)
            at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:250)
            at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
            at org.jboss.Main.boot(Main.java:221)
            at org.jboss.Main$1.run(Main.java:556)
            at java.lang.Thread.run(Thread.java:619)
            Caused by: java.lang.IllegalStateException: ClassLoader has not been set
            at org.jboss.deployers.structure.spi.helpers.AbstractDeploymentUnit.getClassLoader(AbstractDeploymentUnit.java:154)
            at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.addBeanComponent(BeanMetaDataFactoryVisitor.java:60)
            at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:126)
            ... 6 more

            ------------------------------------------------------------------------------------------
            org.jboss.deployers.spi.DeploymentException: Error deploying: file:/D:/WORKSPACES/05_oct_09/dnms/output/DNMS/EMS/server/ems/conf/bootstrap/logging.xml
            at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
            at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:136)
            at org.jboss.system.server.profileservice.ProfileServiceBootstrap.initBootstrapMDs(ProfileServiceBootstrap.java:433)
            at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:250)
            at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
            at org.jboss.Main.boot(Main.java:221)
            at org.jboss.Main$1.run(Main.java:556)
            at java.lang.Thread.run(Thread.java:619)
            Caused by: java.lang.IllegalStateException: ClassLoader has not been set
            at org.jboss.deployers.structure.spi.helpers.AbstractDeploymentUnit.getClassLoader(AbstractDeploymentUnit.java:154)
            at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.addBeanComponent(BeanMetaDataFactoryVisitor.java:60)
            at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:126)
            ... 6 more
            ----------------------------------------------------------------------------------------------

            Once when i get the notification that the jboss is started, any of my methods try for a remote/local lookup, and i am thrown the foll exception. I looked into jmx console and saw nothing(neither my ejb jars, nor my way) is bound to jboss..

            Error in getting Local Object
            javax.naming.NameNotFoundException: myEar 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:726)
            at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
            at javax.naming.InitialContext.lookup(InitialContext.java:392)
            at com.temp.nms.util.LocalLookupManager.getLocalObject(LocalLookupManager.java:55)
            at com.temp.nms.server.startup.PostServerInit.getModules(PostServerInit.java:61)
            at com.temp.nms.server.startup.PostServerInit.doPostOperation(PostServerInit.java:30)
            at com.temp.nms.server.startup.DeploymentChecker.run(DeploymentChecker.java:73)
            2009-11-18 17:34:40,640 ERROR [com.temp.nms.server.startup.PostServerInit] javax.naming.NameNotFoundException: myEar not bound

            • 3. Re: ear not deployed in JBoss start up with derby database
              akhil achuthan Newbie

              Not sure where i missed earlier, but my jboss server also does not look as if started....

              i mean - http://localhost:8080 - does not open up.......

              • 4. Re: ear not deployed in JBoss start up with derby database
                Wolfgang Knauf Master

                Hi akhilachuthan,

                did you define a custom configuration? The path "file:/D:/WORKSPACES/05_oct_09/dnms/output/DNMS/EMS/server/ems/conf/bootstrap/vfs.xml" does not look like the standard JBoss "installation" path. So, what did you do to create this ;-)?

                Wolfgang

                • 5. Re: ear not deployed in JBoss start up with derby database
                  akhil achuthan Newbie

                  thats the JBossVFS initializer configuration file.

                  This derby stuff had worked with me previously when i was using jboss4.

                  • 6. Re: ear not deployed in JBoss start up with derby database
                    Wolfgang Knauf Master

                    Hi,

                    probably my question was not precise enough. Your path indicates that you did not use one of the standard jboss configurations (as "default", "standard", "minimal", "all"), but created a custom configuration. Is this true?
                    Maybe you missed some important part, and the configuration is broken?

                    Best regards

                    Wolfgang

                    • 7. Re: ear not deployed in JBoss start up with derby database
                      akhil achuthan Newbie

                      yup, thats right.. im using my custom configuration as ems.

                      Should that have broken anything?? I will check it out..

                      Is there any configuration specific to the db, that has to be done while using a custom configuration folder.. Coz this same setup works just fine for oracle and mysql, and had worked good when i was using the old jb4... Once after migrating to jboss5 i havnt done anything with derby and now see that its broken. Oracle and mysql works fine even now....

                      • 8. Re: ear not deployed in JBoss start up with derby database
                        Wolfgang Knauf Master

                        Hi,

                        according to the error message, JBoss cannot even startup without your app being deployed to it, so it seems you have missed sometheing when building the configuration. Check this twice, and try to start your server without your app deployed. Probably, it will not start, too.

                        Best regards

                        Wolfgang