| Summary: | transactions atomicity violated by 'transparent' failover in JMS client | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Gordon Sim <gsim> |
| Component: | Release_Notes | Assignee: | Alison Young <alyoung> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Tomas Rusnak <trusnak> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | high | ||
| Version: | 1.3 | CC: | iboverma, lbrindle, trusnak |
| Target Milestone: | 1.3.2 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
C: A bug in the automatic failover mechanism
C: Transactions submited using the JMS client would not have guaranteed atomicity if failover occurred.
F: Do not use automatic failover with JMS client transactions
R:
Text: A bug in the automatic failover mechanism means that transactions submitted using the JMS client will not have guaranteed atomicity if failover occurs. Do not use automatic failover with JMS client transactions if you require guaranteed atomicity.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-02-14 01:51:32 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Gordon Sim
2011-02-09 12:30:59 UTC
Rajith, can you add detail on how to turn off automatic failover please?
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
C: A bug in the automatic failover mechanism
C: Transactions submited using the JMS client would not have guaranteed atomicity if failover occurred.
F: Do not use automatic failover with JMS client transactions
R:
Text: A bug in the automatic failover mechanism means that transactions submitted using the JMS client will not have guaranteed atomicity if failover occurs. Do not use automatic failover with JMS client transactions if you require guaranteed atomicity.
Tech note written without extra detail about disabling automatic failover. Unfortunately, we're out of time to get this extra info in. LKB Revision 0.2 of the release notes will available for review on the stage shortly. Table 2.1 in Chapter 2.2 updated as requested. Workaround included in Release notes at Revision 1-0:
Description:
Transactions submitted using the JMS client would not have guaranteed atomicity if failover occurred. This is due to a bug in the automatic failover mechanism.
Workaround
Do not use automatic failover with JMS client transactions.
>>> VERIFIED
|