Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
5.6.0
-
jdbc persistence adapter, XA
Description
JDBC store does not honor the prepare phase so a broker failure after prepare always results in a rollback which is in violation of the contract.
In the cases where XA is required, the store needs to do its best to respect a prepare outcome.
Having the TM use last resource commit one phase (or the one phase commit optimisation) avoids this issue but is not always possible.
Attachments
Issue Links
- is related to
-
AMQ-3305 Implement "exactly once" delivery with kahaDB and XA in the event of a failure post prepare
- Resolved