5 Replies Latest reply on Jul 12, 2013 3:42 PM by Wolf-Dieter Fink

    errors in startup

    Manjunath Mallela Newbie

      Friends,

       

      i am using clustering concept.

      one server in the cluster started with out any errors. when i am starting the second cluster i am getting the follwing erros. please help me out.

       

      ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Start: name=jboss:database=localDB,service=Hypersonic state=Create mode=Manual requiredState=Installed

      java.sql.SQLException: The database is already in use by another process

      .

      .

      .

      .

      .

      2013-07-11 12:23:53,815 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Real: name=vfsfile:<jboss-home>/server/all/deploy/hsqldb-ds.xml state=PreReal mode=Manual requiredState=Real

      org.jboss.deployers.spi.DeploymentException: Error deploying: jboss:service=Hypersonic,database=localDB

      .

      .

      .

      .

      .

      Caused by: java.sql.SQLException: The database is already in use by another process: org.hsqldb.persist.NIOLockFile@2df9f035[file =<jboss-home>/server/all/data/hypersonic/localDB.lck, exists=true, locked=false, valid=false, fl =null

       

       

       

       

      Please help me here 

       

       

       

      Thanks
      Manjunath M

        • 1. Re: errors in startup
          Wolf-Dieter Fink Master

          HSQL is a 'in memory' database and the files (located in the JBoss data directory) can only be used by one process.

          So maybe you have used a JDBC client and open that files before you start or you have two JBoss instances using the same HSQLDB

          • 2. Re: errors in startup
            Manjunath Mallela Newbie

            Thanks Dieter...

             

            so should we disable/remove the hsql db when we are using the clustering?

            • 3. Re: errors in startup
              Wolf-Dieter Fink Master

              I recommend that as the HSQLDB has issues and should not used for production. You should use a different DB like MySQL, Oracle .....

              You can find wiki pages for your JBoss version to see the different solutions, maybe you can remove the DB if all dependend services are removed or reconfigured

              • 4. Re: errors in startup
                Manjunath Mallela Newbie

                here is what i did today to remove hsqldb

                 

                Removed deploy/hsqldb-ds.xml

                Removed deploy/uuid-key-generator.sar

                Not Remove deploy/messaging

                Remove deploy/juddi-service.sar/ and deploy/snmp-adaptor.sar
                Edited conf/standardjbosscmp-jdbc.xml, and commented out the defaults section

                Edited conf/login-config.xml, and removed the "HsqlDbRealm" application-policy

                Edited deploy/ejb2-timer-service.xml to comment out the database persistence policy, comment in the noop persistence policy, and change the EJBTimerServiceImpl persistence policy to noop from database

                 

                 

                 

                below is the ejb2-timer-service.xml

                 

                 

                 

                <server>

                  <!-- ==================================================================== -->
                  <!-- J2EE Timer Service                                                   -->
                  <!-- ==================================================================== -->

                  <!--
                    A persistence policy that persists timers to a database.
                   
                    The 2 supported db persistence plugins are:
                      org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin
                      org.jboss.ejb.txtimer.OracleDatabasePersistencePlugin
                     
                    The table name defaults to "TIMERS". It can be overriden using the
                    'TimersTable' attribute if the persistence plugin supports it.
                    When overriding the timers table, an optional schema can be specified
                    using the syntax [schema.]table
                  -->

                  <!--
                  <mbean code="org.jboss.ejb.txtimer.DatabasePersistencePolicy" name="jboss.ejb:service=EJBTimerService,persistencePolicy=database">
                    <depends optional-attribute-name="DataSource">jboss.jca:service=DataSourceBinding,name=DefaultDS</depends>
                    <attribute name="DatabasePersistencePlugin">org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin</attribute>
                    <attribute name="TimersTable">TIMERS</attribute>
                    <depends>jboss.jdbc:datasource=DefaultDS,service=metadata</depends>
                  </mbean>
                  -->

                  <!-- A persistence policy that does not persist the timer -->
                  <mbean code="org.jboss.ejb.txtimer.NoopPersistencePolicy" name="jboss.ejb:service=EJBTimerService,persistencePolicy=noop"/>
                  
                   <!-- A retry policy that uses a fixed interval in milli seconds -->
                   <mbean code="org.jboss.ejb.txtimer.FixedDelayRetryPolicy" name="jboss.ejb:service=EJBTimerService,retryPolicy=fixedDelay">
                     <attribute name="Delay">100</attribute>
                   </mbean>

                  <!-- An EJB Timer Service that is Tx aware -->
                  <mbean code="org.jboss.ejb.txtimer.EJBTimerServiceImpl"
                    name="jboss.ejb:service=EJBTimerService">
                    <attribute name="TimerIdGeneratorClassName">org.jboss.ejb.txtimer.BigIntegerTimerIdGenerator</attribute>
                    <attribute name="TimedObjectInvokerClassName">org.jboss.ejb.txtimer.TimedObjectInvokerImpl</attribute>
                    <depends optional-attribute-name="RetryPolicy">jboss.ejb:service=EJBTimerService,retryPolicy=fixedDelay</depends>
                    <depends optional-attribute-name="PersistencePolicy">jboss.ejb:service=EJBTimerService,persistencePolicy=noop</depends>
                    <depends optional-attribute-name="TransactionManagerFactory" proxy-type="org.jboss.tm.TransactionManagerFactory">
                      jboss:service=TransactionManager
                    </depends>   
                  </mbean>
                ----------------------------------------------

                 

                what else i need to do..

                now i am getting the below errors

                 

                ---------------------------------------------

                07:54:38,774 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

                DEPLOYMENTS MISSING DEPENDENCIES:
                  Deployment "jboss.jca:name=JmsXA,service=ConnectionFactoryBinding" is missing the following dependencies:
                    Dependency "jboss.jca:name=JmsXA,service=TxCM" (should be in state "Create", but is actually in state "Configured")
                  Deployment "jboss.jca:name=JmsXA,service=ManagedConnectionFactory" is missing the following dependencies:
                    Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")
                  Deployment "jboss.jca:name=JmsXA,service=ManagedConnectionPool" is missing the following dependencies:
                    Dependency "jboss.jca:name=JmsXA,service=ManagedConnectionFactory" (should be in state "Create", but is actually in state "Configured")
                  Deployment "jboss.jca:name=JmsXA,service=TxCM" is missing the following dependencies:
                    Dependency "jboss.jca:name=JmsXA,service=ManagedConnectionPool" (should be in state "Create", but is actually in state "Configured")
                  Deployment "jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory" is missing the following dependencies:
                    Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")
                    Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.messaging:service=PostOffice' **")
                  Deployment "jboss.messaging.connectionfactory:service=ClusteredConnectionFactory" is missing the following dependencies:
                    Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.messaging:service=PostOffice' **")
                    Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")
                  Deployment "jboss.messaging.connectionfactory:service=ConnectionFactory" is missing the following dependencies:
                    Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")
                    Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.messaging:service=PostOffice' **")
                  Deployment "jboss.messaging.destination:name=DLQ,service=Queue" is missing the following dependencies:
                    Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.messaging:service=PostOffice' **")
                    Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")
                  Deployment "jboss.messaging.destination:name=ExpiryQueue,service=Queue" is missing the following dependencies:
                    Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")
                    Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.messaging:service=PostOffice' **")
                  Deployment "jboss.messaging:service=ServerPeer" is missing the following dependencies:
                    Dependency "jboss.messaging:service=JMSUserManager" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.messaging:service=JMSUserManager' *
                *")
                    Dependency "jboss.messaging:service=PersistenceManager" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.messaging:service=PersistenceMa
                nager' **")
                  Deployment "jboss.mq:service=DestinationManager" is missing the following dependencies:
                    Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")
                  Deployment "jboss:service=KeyGeneratorFactory,type=HiLo" is missing the following dependencies:
                    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,serv
                ice=DataSourceBinding' **")
                  Deployment "jboss:service=juddi" is missing the following dependencies:
                    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,serv
                ice=DataSourceBinding' **")

                DEPLOYMENTS IN ERROR:
                  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=DataSource
                Binding' **
                  Deployment "jboss.messaging:service=PersistenceManager" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.messaging:service=PersistenceManager' **
                  Deployment "jboss.messaging:service=JMSUserManager" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.messaging:service=JMSUserManager' **
                  Deployment "jboss.messaging:service=PostOffice" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.messaging:service=PostOffice' **
                ----------------------------------------------

                • 5. Re: errors in startup
                  Wolf-Dieter Fink Master

                  The reason might be before the summary. You might look for the first error or warning.

                   

                  Other option is to start removing one service after the other and reconfigure things.

                  The messaging system might need the database, depend on the real version it might be JBossMQ JBossMessaging or HornetQ