Loading...

XML

Word

Printable

Details

Type: Sub-task
Resolution: Done
Priority: Major
Fix Version/s: EAP_EWP 5.1.2 ER2
Affects Version/s: None
Component/s: Documentation
Labels:
None

Release Note Text:

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.
Release Note Status:
Documented as Resolved Issue
Docs QE Status:
ON_QA

Description

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.

Attachments

Activity

People

Assignee:: Pavel Slavicek

Reporter:: Pavel Slavicek

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: 2011/07/18 7:53 AM

Updated:: 2011/11/24 4:08 AM

Resolved:: 2011/09/27 8:25 PM