Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-6620

EAP won't start in default profile with all databases

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • EAP_EWP 5.1.2 ER1
    • EAP_EWP 5.1.1 ER2
    • Messaging
    • None
    • Hide
      The messaging server would not start in default profile when configured to use a database other than HSQLDB database. This was caused by not commenting out lines in the <filename>database_type-persistence-service.xml</filename> file that were applicable only to clustered profiles.
      The fix adds prescriptive comments to the <filename>database_type-persistence-service.xml</filename> file, instructing how to comment out unnecessary configuration directives for non-clustered messaging server instances.
      Show
      The messaging server would not start in default profile when configured to use a database other than HSQLDB database. This was caused by not commenting out lines in the <filename>database_type-persistence-service.xml</filename> file that were applicable only to clustered profiles. The fix adds prescriptive comments to the <filename>database_type-persistence-service.xml</filename> file, instructing how to comment out unnecessary configuration directives for non-clustered messaging server instances.
    • Documented as Resolved Issue
    • NEW

    Description

      When EAP server is configured to use mysql db(mysql-peristence-service.xml, mysql-ds.xml from docs) in default profile then server won't start correctly.

      Errors message on standard output:

      13:10:30,523 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
      DEPLOYMENTS MISSING DEPENDENCIES:
      Deployment "jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory" is missing the following dependencies:
      Dependency "jboss.messaging.connectionfactory:service=ClusteredConnectionFactory" (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 "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' **")
      DEPLOYMENTS IN ERROR:
      Deployment "jboss.jgroups:service=ChannelFactory" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jgroups:service=ChannelFactory' **

      Attachments

        Activity

          People

            jaredmorgs_jira Jared Morgan (Inactive)
            mnovak1@redhat.com Miroslav Novak
            Jared Morgan Jared Morgan (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: