2 Replies Latest reply on Jul 12, 2010 5:18 PM by Zemian Deng

    Problem in JBoss.5.1.0 GA Startup

    Younes Yahyaoui Novice

      Hi,

       

      Inorder to build JBossMessaging Clustering i have tried to change the database for dataSource form hsqlDB to MysqlDB. I use JBoss AS 5.1.0-GA.

      I have done the following steps:

       

      1. change hsqldb-persistence-service.xml to mysqldb-service.xml (which is found in $serverhome$/docs/examples/jms) and copy it under $server-home$/server/default/deploy/messaging
      2. change the default datasotre from DefaultDS to MySqlDS

       

      Then i habe tried to start the JBossAS Server. The following Probleme were occured:

       

       

      11:52:15,485 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
      DEPLOYMENTS MISSING DEPENDENCIES:
        Deployment "JBossTimerServiceFactory" is missing the following dependencies:
          Dependency "jboss.ejb:service=EJBTimerService" (should be in state "Create", but is actually in state "Configured")
        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")
        Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3" is missing the following dependencies:
          Dependency "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **")
        Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3_endpoint" is missing the following dependencies:
          Dependency "jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3" (should be in state "Configured", but is actually in state "PreInstall")
        Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3" is missing the following dependencies:
          Dependency "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **")
        Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3_endpoint" is missing the following dependencies:
          Dependency "jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3" (should be in state "Configured", but is actually in state "PreInstall")
        Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3" is missing the following dependencies:
          Dependency "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **")
          Dependency "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jndi:SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView' **")
        Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3_endpoint" is missing the following dependencies:
          Dependency "jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3" (should be in state "Configured", but is actually in state "PreInstall")
        Deployment "jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory" is missing the following dependencies:
          Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "Configured")
        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 "Configured")
        Deployment "jboss.messaging.connectionfactory:service=ConnectionFactory" is missing the following dependencies:
          Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "Configured")
        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 "Configured")
        Deployment "jboss.messaging.destination:name=ExpiryQueue,service=Queue" is missing the following dependencies:
          Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "Configured")
        Deployment "jboss.messaging:service=PostOffice" is missing the following dependencies:
          Dependency "jboss.jgroups:service=ChannelFactory" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jgroups:service=ChannelFactory' **")
        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,service=DataSourceBinding' **")
      DEPLOYMENTS IN ERROR:
        Deployment "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **, ** UNRESOLVED Demands 'jndi:SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView' **
        Deployment "jboss.jgroups:service=ChannelFactory" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jgroups:service=ChannelFactory' **
        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 "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **
        Deployment "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **
        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' **


      can someone tell me whaht is the problem. I will appreciate any help.

       

      regards

       

      younes

        • 1. Re: Problem in JBoss.5.1.0 GA Startup
          Peter Johnson Master

          Looks like you removed hsqldb-ds.xml which defines the DefaultDS datasource. There are services other than messaging that use DefaultDS. Either you need to restore hsqldb-ds.xml so that those services can continue to run, or you need to change those services to also use the new MySqlDS data source.

           

          I'd point you to the wiki page on convert DefaultDS to use MySQL, but that page is 3 years old and not probably not relevant for 5.1. One sure-fire way is to search the *.xml files for occurances of the name DefaultDS - that will tell you every service that uses that data source.

          • 2. Re: Problem in JBoss.5.1.0 GA Startup
            Zemian Deng Apprentice

            Peter is right that your DefaultDS is not correctly configured.

             

            It will be easier if you setup and rename the new MySqlDS to DefaultDS. If you start off with a clean JBOSS_HOME/server/default profile directory, follow these steps to switch to MySql datastore for jboss-5.1.0:

             

            1. Rename JBOSS_HOME/server/defualt/hsqldb-ds.xml to hsqldb-ds.xml.bak

            2. Copy JBOSS_HOME/docs/examples/jca/mysql-ds.xml to JBOSS_HOME/server/default/deploy/mysql-ds.xml

            3. Edit JBOSS_HOME/server/default/deploy/mysql-ds.xml and replace MySqlDS to DefaultDS

            4. Edit JBOSS_HOME/server/default/deploy/mysql-ds.xml and add <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>

                (This is needed for JBossMessing)

            5. Rename JBOSS_HOME/server/default/deploy/messaging/hsqldb-persistence-service.xml to JBOSS_HOME/server/default/deploy/messaging/hsqldb-persistence-service.xml.bak

            6. Copy JBOSS_HOME/docs/examples/mysql-persistence-service.xml into JBOSS_HOME/server/default/deploy/messaging/mysql-persistence-service.xml

             

            TIPS: Do not change local-tx-datasource to xa-datasource for DefaultDS. If you need XA DataSource for your application, I would recommand you create a new file with new name like MyXAAppDS (an example of this is not in JBoss5 for some reason, but you can find one in JBoss-6.M3). JBossMessaging doesn't need xa-datasource to have JMS tx supports, and changing your DefaultDS to XA will give you much grief!