2 Replies Latest reply on Dec 6, 2010 10:31 AM by mike just

    Bunch of errors when deploying JBoss 6.0.0.CR1

    mike just Master

      Anyone has any idea on following errors? Any suggestions will be really appreciated.

       

      DEPLOYMENTS MISSING DEPENDENCIES:
        Deployment "jboss.ejb:persistencePolicy=database,service=EJBTimerService" is missing the following dependencies:
          Dependency "jboss.jdbc:datasource=DefaultDS,service=metadata" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jdbc:datasource=DefaultDS,service=metadata' **")
          Dependency "jboss.jca:name=DefaultDS,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=DefaultDS,service=DataSourceBinding' **")
        Deployment "jboss.ejb:service=EJBTimerService" is missing the following dependencies:
          Dependency "jboss.ejb:persistencePolicy=database,service=EJBTimerService" (should be in state "Create", but is actually in state "Configured")

      DEPLOYMENTS IN ERROR:
        Deployment "org.hornetq:module=JMS,name="NettyThroughputConnectionFactory",type=ConnectionFactory" is in error due to the following reason(s): java.lang.LinkageError: loader constraint violation: loader (instance of <bootloader>) previously initiated loading for a different type with name "javax/transaction/xa/XAResource"
        Deployment "vfs:///C:/Welocalize/globalsight/server/GlobalSight_20101206/GlobalSight/jboss/jboss_server/server/default/deploy/hornetq/jms-ds.xml" is in error due to the following reason(s): java.lang.LinkageError: loader constraint violation: loader (instance of <bootloader>) previously initiated loading for a different type with name "javax/transaction/xa/XAResource"
        Deployment "jboss.jca:name=DefaultDS,service=DataSourceBinding" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name=DefaultDS,service=DataSourceBinding' **
        Deployment "vfs:///C:/Welocalize/globalsight/server/GlobalSight_20101206/GlobalSight/jboss/jboss_server/server/default/deploy/jms-ra.rar" is in error due to the following reason(s): java.lang.LinkageError: loader constraint violation: loader (instance of <bootloader>) previously initiated loading for a different type with name "javax/transaction/xa/XAResource"
        Deployment "org.hornetq:module=JMS,name="NettyConnectionFactory",type=ConnectionFactory" is in error due to the following reason(s): java.lang.LinkageError: loader constraint violation: loader (instance of <bootloader>) previously initiated loading for a different type with name "javax/transaction/xa/XAResource"
        Deployment "vfs:///C:/Welocalize/globalsight/server/GlobalSight_20101206/GlobalSight/jboss/jboss_server/server/default/deploy/hsqldb-ds.xml" is in error due to the following reason(s): java.lang.LinkageError: loader constraint violation: loader (instance of <bootloader>) previously initiated loading for a different type with name "javax/transaction/xa/XAResource"
        Deployment "org.hornetq:module=JMS,name="InVMConnectionFactory",type=ConnectionFactory" is in error due to the following reason(s): java.lang.LinkageError: loader constraint violation: loader (instance of <bootloader>) previously initiated loading for a different type with name "javax/transaction/xa/XAResource"
        Deployment "jboss.jdbc:datasource=DefaultDS,service=metadata" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jdbc:datasource=DefaultDS,service=metadata' **

              at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1228) [:2.2.0.Alpha8]
              at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:905) [:2.2.0.Alpha8]
              at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.checkComplete(MainDeployerPlugin.java:87) [:6.0.0.20101110-CR1]
              at org.jboss.profileservice.deployment.ProfileDeployerPluginRegistry.checkAllComplete(ProfileDeployerPluginRegistry.java:118) [:0.1.0.Alpha1]
              at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:133) [:6.0.0.20101110-CR1]
              at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:56) [:6.0.0.20101110-CR1]
              at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
              at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
              at java.lang.Thread.run(Thread.java:619) [:1.6.0_07]

        • 1. Re: Bunch of errors when deploying JBoss 6.0.0.CR1
          jaikiran pai Master

          Did you change something with the hsqldb-ds.xml?

          • 2. Re: Bunch of errors when deploying JBoss 6.0.0.CR1
            mike just Master

            NO.

             

             

            Its original look:

             

            <?xml version="1.0" encoding="UTF-8"?>

            <!-- The Hypersonic embedded database JCA connection factory config -->

            <!-- See http://www.jboss.org/community/wiki/Multiple1PC for information about local-tx-datasource -->
            <!-- $Id: hsqldb-ds.xml 97536 2009-12-08 14:05:07Z jesper.pedersen $ -->

            <datasources>
               <local-tx-datasource>

                  <!-- The jndi name of the DataSource, it is prefixed with java:/ -->
                  <!-- Datasources are not available outside the virtual machine -->
                  <jndi-name>DefaultDS</jndi-name>

                  <!-- For server mode db, allowing other processes to use hsqldb over tcp.
                  This requires the org.jboss.jdbc.HypersonicDatabase mbean.
                  <connection-url>jdbc:hsqldb:hsql://${jboss.bind.address}:1701</connection-url>
                  -->
                  <!-- For totally in-memory db, not saved when jboss stops.
                  The org.jboss.jdbc.HypersonicDatabase mbean is required for proper db shutdown
                  <connection-url>jdbc:hsqldb:.</connection-url>
                  -->
                  <!-- For in-process persistent db, saved when jboss stops.
                  The org.jboss.jdbc.HypersonicDatabase mbean is required for proper db shutdown
                  -->
                  <connection-url>jdbc:hsqldb:${jboss.server.data.dir}${/}hypersonic${/}localDB</connection-url>

                  <!-- The driver class -->
                  <driver-class>org.hsqldb.jdbcDriver</driver-class>

                  <!-- The login and password -->
                  <user-name>sa</user-name>
                  <password></password>

                  <!--example of how to specify class that determines if exception means connection should be destroyed-->
                  <!--exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.DummyExceptionSorter</exception-sorter-class-name-->

                  <!-- this will be run before a managed connection is removed from the pool for use by a client-->
                  <!--<check-valid-connection-sql>select * from something</check-valid-connection-sql> -->

                  <!-- The minimum connections in a pool/sub-pool. Pools are lazily constructed on first use -->
                  <min-pool-size>5</min-pool-size>

                  <!-- The maximum connections in a pool/sub-pool -->
                  <max-pool-size>20</max-pool-size>

                  <!-- The time before an unused connection is destroyed -->
                  <!-- NOTE: This is the check period. It will be destroyed somewhere between 1x and 2x this timeout after last use -->
                  <!-- TEMPORARY FIX! - Disable idle connection removal, HSQLDB has a problem with not reaping threads on closed connections -->
                  <idle-timeout-minutes>0</idle-timeout-minutes>

                  <!-- sql to call when connection is created
                    <new-connection-sql>some arbitrary sql</new-connection-sql>
                  -->

                  <!-- sql to call on an existing pooled connection when it is obtained from pool
                     <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
                  -->

                  <!-- example of how to specify a class that determines a connection is valid before it is handed out from the pool
                     <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.DummyValidConnectionChecker</valid-connection-checker-class-name>
                  -->

                  <!-- Whether to check all statements are closed when the connection is returned to the pool,
                       this is a debugging feature that should be turned off in production -->
                  <track-statements/>

                  <!-- Use the getConnection(user, pw) for logins
                    <application-managed-security/>
                  -->

                  <!-- Use the security domain defined in conf/login-config.xml -->
                  <security-domain>HsqlDbRealm</security-domain>

                  <!-- Use the security domain defined in conf/login-config.xml or the
                       getConnection(user, pw) for logins. The security domain takes precedence.
                    <security-domain-and-application>HsqlDbRealm</security-domain-and-application>
                  -->

                  <!-- HSQL DB benefits from prepared statement caching -->
                  <prepared-statement-cache-size>32</prepared-statement-cache-size>

                  <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
                  <metadata>
                     <type-mapping>Hypersonic SQL</type-mapping>
                  </metadata>

                  <!-- When using in-process (standalone) mode -->
                  <depends>jboss:service=Hypersonic,database=localDB</depends>
                  <!-- Uncomment when using hsqldb in server mode
                  <depends>jboss:service=Hypersonic</depends>
                  -->
               </local-tx-datasource>

               <!-- Uncomment if you want hsqldb accessed over tcp (server mode)
               <mbean code="org.jboss.jdbc.HypersonicDatabase"
                 name="jboss:service=Hypersonic">
                 <attribute name="Port">       
                    <value-factory bean="ServiceBindingManager" method="getIntBinding"
                       parameter="jboss:service=Hypersonic"/>
                 </attribute>
                 <attribute name="BindAddress">       
                    <value-factory bean="ServiceBindingManager" method="getStringBinding"
                       parameter="jboss:service=Hypersonic"/>
                 </attribute>    
                 <attribute name="Silent">true</attribute>
                 <attribute name="Database">default</attribute>
                 <attribute name="Trace">false</attribute>
                 <attribute name="No_system_exit">true</attribute>
               </mbean>
               -->

               <!-- For hsqldb accessed from jboss only, in-process (standalone) mode -->
               <mbean code="org.jboss.jdbc.HypersonicDatabase"
                 name="jboss:service=Hypersonic,database=localDB">
                 <attribute name="Database">localDB</attribute>
                 <attribute name="InProcessMode">true</attribute>
               </mbean>
              
            </datasources>