2 Replies Latest reply on Jan 19, 2016 6:05 AM by Tomaz Cerar

    Impact of WFLY-4592 on legacy systems

    Syed Mahdi Apprentice

      Hello Wildfly devs and users,

       

      I just stumbled upon this: [WFLY-4592] Deprecate messaging subsystem - JBoss Issue Tracker  and we just migrated our applications from jboss 4 to wildfly 9 with java 8 and converted all the jboss configuration to the new standalone.xml style configurations. Now going forward Wildfly 10 won't have the messaging subsystem (deprecated or will it actually be removed totally?).  How will this impact people like me who have their subsystems messaging and rely on hornetq. as the new subsystem is messaging-activemq subsystem. With HornetQ removed (as per subtask in the Jira) will we have to migrate to Active MQ then when we goto WF10.

       

      2) Also, Any particular reason why HornetQ will be removed and ActiveMQ will be used going forward.

      3) What is the time frame of this change. We just migrated to WF9 and we have not even hit production with it. I am sure WF 9 will still be supported on forums and all but is it prudent to go with something that has been deprecated to production now.

      4) is there a conversion guide for people to port their HornetQ subsystems to the new messaging-activemq subsystem.  ([WFLY-4587] Provide a migration management operation for HornetQ to ActiveMQ Artemis - JBoss Issue Tracker  Already answered this one but a guide to use the :migrate will be nice as well)

       

      Thanks

      Syed

        • 1. Re: Impact of WFLY-4592 on legacy systems
          Justin Bertram Master

          Now going forward Wildfly 10 won't have the messaging subsystem (deprecated or will it actually be removed totally?)

          My understanding is that it will be deprecated and then removed completely in a subsequent release.

           

          How will this impact people like me who have their subsystems messaging and rely on hornetq. as the new subsystem is messaging-activemq subsystem. With HornetQ removed (as per subtask in the Jira) will we have to migrate to Active MQ then when we goto WF10.

          You will need to migrate, but I don't expect you'll have much trouble.  About a year and a half ago now the HornetQ code-base was donated to Apache ActiveMQ and has become Apache ActiveMQ Artemis.  This is the broker that will be integrated in the new subsystem.  It will support old HornetQ clients and the configuration will be very similar to what you use today.

           

          2) Also, Any particular reason why HornetQ will be removed and ActiveMQ will be used going forward.

          As indicated previously, HornetQ has been donated to Apache ActiveMQ and no further development will be done on HornetQ.  The new Artemis broker has already had 3 releases.  See more at http://activemq.apache.org/artemis/.

           

          3) What is the time frame of this change. We just migrated to WF9 and we have not even hit production with it. I am sure WF 9 will still be supported on forums and all but is it prudent to go with something that has been deprecated to production now.

          WF 10 has already integrated Artemis.  I'm not sure when the old messaging subsystem will be removed but there will certainly be no more HornetQ releases so any bugs you run into will go unfixed.

           

          To be clear, there is no kind of official support for community projects like Wildfly, HornetQ, and Artemis.  If you want real support you should get in touch with Red Hat about a support subscription.

           

          4) is there a conversion guide for people to port their HornetQ subsystems to the new messaging-activemq subsystem.  ([WFLY-4587] Provide a migration management operation for HornetQ to ActiveMQ Artemis - JBoss Issue Tracker  Already answered this one but a guide to use the :migrate will be nice as well)

          I'm not aware of any specific conversion guide.  However, given that both HornetQ and Artemis come from the same code-base I doubt the conversion will be terribly difficult.

          • 2. Re: Impact of WFLY-4592 on legacy systems
            Tomaz Cerar Master

            Now going forward WildFly 10 won't have the messaging subsystem (deprecated or will it actually be removed totally?).

            Yes it is practically already removed in WF 10, I say practically because the management "stub" is still there which allows you to manage legacy servers when running in domain mode and DC is on 10.

             

            With HornetQ removed (as per subtask in the Jira) will we have to migrate to Active MQ then when we goto WF10.

            Yes you will need to migrate to new subsystem once you upgrade to WildFly 10

             

            3) What is the time frame of this change. We just migrated to WF9 and we have not even hit production with it. I am sure WF 9 will still be supported on forums and all but is it prudent to go with something that has been deprecated to production now.

            It is already done and well tested, WildFly 10 is about to hit .Final release. If you are not in production yet I would recommend you to go with WildFly 10 CR5 now and upgrade to .Final which is about to be released, as CR5 was last candidate release.

             

            4) is there a conversion guide for people to port their HornetQ subsystems to the new messaging-activemq subsystem.  ([WFLY-4587] Provide a migration management operation for HornetQ to ActiveMQ Artemis - JBoss Issue Tracker  Already answered this one but a guide to use the :migrate will be nice as well)

            All subsystems that ware removed/replaced from older versions have standard :migrate operation that migrates config to new one if possible (sometimes some configuration options cannot be migrated automatically)

            It is quite simple, just grab WildFly 10 and start it in admin-mode with old standalone.xml (or whatever name of your config is). and run :migrate operation on subsystems you want to migrate.

             

            so basically you do,

            - standalone.sh|ps1|bat --admin-mode

            - run jboss-cli, and run /subsystem=messaging:migrate

             

            But that only migrates configuration, not data in messaging datastore.