Bug 676303 - transactions atomicity violated by 'transparent' failover in JMS client
Summary: transactions atomicity violated by 'transparent' failover in JMS client
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: Release_Notes
Version: 1.3
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: 1.3.2
: ---
Assignee: Alison Young
QA Contact: Tomas Rusnak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-09 12:30 UTC by Gordon Sim
Modified: 2011-02-14 01:51 UTC (History)
3 users (show)

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.
Clone Of:
Environment:
Last Closed: 2011-02-14 01:51:32 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Gordon Sim 2011-02-09 12:30:59 UTC 
If using transactions with the JMS client, you need to turn off automatic failover or you risk losing the atomicity guarantees when failover occurs.

See bug 667428
Comment 1 Gordon Sim 2011-02-09 12:32:36 UTC 
Rajith, can you add detail on how to turn off automatic failover please?
Comment 2 Lana Brindley 2011-02-11 00:00:20 UTC 
    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.
Comment 3 Lana Brindley 2011-02-11 00:02:39 UTC 
Tech note written without extra detail about disabling automatic failover. Unfortunately, we're out of time to get this extra info in.

LKB
Comment 4 Alison Young 2011-02-11 00:51:42 UTC 
Revision 0.2 of the release notes will available for review on the stage
shortly.
Comment 5 Tomas Rusnak 2011-02-11 10:55:41 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.