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

CLONE - Empty messaging subsystem can not be persisted

XMLWordPrintable

    • Icon: Support Patch Support Patch
    • Resolution: Done
    • Icon: Major Major
    • One Off Releases
    • EAP 6.0.0
    • Messaging
    • None

    • EAP 6.0.0

    • eap-6.0.0-JBPAPP-10363
    • Hide
      PATCH NAME:
              JBPAPP-10363
      PRODUCT NAME:
              JBoss Enterprise Application Platform (EAP)
      VERSION:
              6.0.0
      SHORT DESCRIPTION:
              Empty messaging subsystem can not be persisted
      LONG DESCRIPTION:
              Adding the messaging subsystem from scratch by using the CLI will fail as it expects to have a hornetq server defined.
      MANUAL INSTALL INSTRUCTIONS:
              1. Rename $JBOSS/modules/org/jboss/as/messaging/main
                  to $JBOSS/modules/org/jboss/as/messaging/original_600
                  as a backup
              2. Create a new directory: $JBOSS/modules/org/jboss/as/messaging/main
              3. unzip the patch into this directory. This will give you:
                  - jboss-as-messaging-7.1.2.Final-redhat-1_JBPAPP-10363.jar
                  - module_JBPAPP-10363.xml
               4. Rename module_JBPAPP-10363.xml to module.xml
      COMPATIBILITY:
              N/A
      DEPENDENCIES:
              N/A
      SUPERSEDES:
              N/A
      SUPERSEDED BY:
              JBoss EAP 6.0.1
      CREATOR:
              Tom Fonteyne
      DATE:
              7-nov-2012
      Show
      PATCH NAME:          JBPAPP-10363 PRODUCT NAME:         JBoss Enterprise Application Platform (EAP) VERSION:         6.0.0 SHORT DESCRIPTION:         Empty messaging subsystem can not be persisted LONG DESCRIPTION:         Adding the messaging subsystem from scratch by using the CLI will fail as it expects to have a hornetq server defined. MANUAL INSTALL INSTRUCTIONS:         1. Rename $JBOSS/modules/org/jboss/as/messaging/main             to $JBOSS/modules/org/jboss/as/messaging/original_600             as a backup         2. Create a new directory: $JBOSS/modules/org/jboss/as/messaging/main         3. unzip the patch into this directory. This will give you:             - jboss-as-messaging-7.1.2.Final-redhat-1_ JBPAPP-10363 .jar             - module_ JBPAPP-10363 .xml          4. Rename module_ JBPAPP-10363 .xml to module.xml COMPATIBILITY:         N/A DEPENDENCIES:         N/A SUPERSEDES:         N/A SUPERSEDED BY:         JBoss EAP 6.0.1 CREATOR:         Tom Fonteyne DATE:         7-nov-2012
    • Low
    • Adding the messaging subsystem from scratch by using the CLI will fail in JBoss EAP 6.0.0 as it expects to have a hornetq server defined. This patch makes this possible.
    • NEW

      When the messaging subsystem is persisted, it requires to have defined hornetq-server nodes but that's not correct.

      E.g. when the messaging subsystem is added through the CLI, it should be marshalled even though there is no hornetq-server

      The XSD for the messaging subsystem is correct: minOccurs for hornetq-server element is 0.

              jbn-patch-team JBN Patch Team list
              tfonteyn Tom Fonteyne (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: