Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-4587

Provide a migration management operation for HornetQ to ActiveMQ Artemis

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 10.0.0.Alpha6
    • None
    • JMS
    • None

    Description

      WildFly 10 has a new messaging-activemq subsystem using ActiveMQ Artemis as its messaging broker.

      WildFly 10 needs to provide a :migrate management operation so that user upgrading from WildFly 9 to 10 can start WildFly 10 with their old configuration (which used HornetQ) and migrate to the new subsystem (which used ActiveMQ Artemis).

      This migrate operation deals only with the management resource and does not migrate data from HornetQ to Artemis. This will done in a separate step (using either a JMS bridge or data export tool)

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. WFLY-5004 Messaging migration does not work in domain mode

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. WFLY-4592 Deprecate messaging subsystem

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Task - Represents a small unit of work that is not end-user facing. WFLY-4584 Use Apache ActiveMQ Artemis as the messaging broker

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              jmesnil1@redhat.com Jeff Mesnil
              jmesnil1@redhat.com Jeff Mesnil
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: