Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-6808 HornetQ User Guide Cover To Cover Review
  3. JBPAPP-6849

Update information about migration from JBoss Messaging to HornetQ

XMLWordPrintable

    • Hide
      The "Migrating to HornetQ" section did not contain specific information about migrating JBoss Messaging applications where High Availability was concerned. A new section "Client-side Failure Handling" is now available in the guide, which details the extra code required to correctly handle HornetQ failover exceptions.
      Show
      The "Migrating to HornetQ" section did not contain specific information about migrating JBoss Messaging applications where High Availability was concerned. A new section "Client-side Failure Handling" is now available in the guide, which details the extra code required to correctly handle HornetQ failover exceptions.
    • Documented as Resolved Issue
    • ON_QA

      Hi Jared,
      section "Chapter 2. Migrating to HornetQ" contains following information for the customers:
      "If you are using standard JMS in your application there is no need to change your source code."

      But we have found quite different behavior of the JBM and the HornetQ in the critical situations. We think that this feature should be documented (see discussions on JBPAPP-6763 and on the PM list). Customers should have information about this different behavior (small information + link to the examples how to do it) included in the documentation related to migration from JBoss Messaging to HornetQ.

      Please try to ping Clebert for more information.

              pslavice@redhat.com Pavel Slavicek
              pslavice@redhat.com Pavel Slavicek
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: