Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 886969

Summary:	Add fix for 6.0.1 docs (Transactions)
Product:	[JBoss] JBoss Data Grid 6	Reporter:	Martin Gencur <mgencur>
Component:	Documentation	Assignee:	Misha H. Ali <mhusnain>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.0.1	CC:	jdg-bugs
Target Milestone:	---
Target Release:	6.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-01-21 23:57:48 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Comment 1 Misha H. Ali 2012-12-13 23:26:14 UTC

Thanks Martin. I am working on the other transactions bug so I'll incorporate this into the material.

Comment 2 Misha H. Ali 2012-12-17 06:03:57 UTC

Thanks very much for clarifying that, Martin. Developing topics with updated information now.

Comment 3 Martin Gencur 2012-12-18 08:06:33 UTC

Hi Misha, it seems the JDG 6.1 will really contain the fix for this issue. Please see https://issues.jboss.org/browse/ISPN-2552. We have not tested it yet but I guess this BZ becomes out of date - or maybe it could be a fix for 6.0.1 documentation if applicable.

Comment 4 Misha H. Ali 2013-01-02 02:05:23 UTC

Checking into translation ramifications of adding this fix to the 6.0.x documentation.

Comment 5 Misha H. Ali 2013-01-14 04:28:17 UTC

Sent reminder to Takuro (in charge of JDG Japanese translation). If I don't hear from him within a week I will go ahead and implement the changes and send him a notification to work out the JP transaction change needed.

Also changing the title to more accurately reflect the work for this bug.

Comment 6 Misha H. Ali 2013-01-15 07:25:47 UTC

Added note and brewed. Will tag Martin to QA when this is available on the stage.

Comment 8 Martin Gencur 2013-01-18 12:08:37 UTC

Misha,
could we change the last sentence from "This occurs because non-transactional caches acquire locks on each node they write on, which causes a deadlock even if the transaction writes to a single key." 

to something like this?: 

"This occurs because non-transactional caches acquire locks on each node they write on. Using transactions will prevent deadlocks as caches will acquire locks on a single node."


Feel free to rephrase it but I think mentioning "transaction with single key" will confuse users as they suppose this problem occurs only for non-transactional caches.

Thanks

Comment 10 Misha H. Ali 2013-01-21 23:57:48 UTC

This is now available on the CSP:

https://access.redhat.com/knowledge/docs/en-US/JBoss_Data_Grid/6/html/Administration_and_Configuration_Guide/chap-Transactions.html#About_Java_Transaction_API_Transactions

Marking all comments with internal URLs private and setting this bug to current release.