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

Bug 1047908

Summary:	WriteSkew not throwing an exception for AtomicMap in REPL and DIST mode
Product:	[JBoss] JBoss Data Grid 6	Reporter:	Shay Matasaro <smatasar>
Component:	Infinispan	Assignee:	Pedro Ruivo <pruivo>
Status:	CLOSED UPSTREAM	QA Contact:	Martin Gencur <mgencur>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.1.0	CC:	jdg-bugs, pruivo, ttarrant, vjuranek
Target Milestone:	CR1
Target Release:	6.2.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	The writeSkewCheck flag does not work correctly for AtomicMap. When JBoss Data Grid runs in REPEATABLE_READ isolation mode for transactions, the writeSkewCheck flag is enabled, and two concurrent transactions read/write data from the same AtomicMap. The WriteSkewException exception is never thrown when committing either of the transactions. </para> <para> Consequently, the data stored in the AtomicMap might be changed by another transaction, and current transaction will not register this change during commit.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-02-10 03:34:44 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:

Description Shay Matasaro 2014-01-02 14:41:58 UTC

With WriteSkew enabled and REPEATABLE_READ enabled, changing AtomicMap values during a transaction and then attempting to read or write these values , does not throw any WriteSkew exception.

This happens for both  DIST and REPL in local mode.

Comment 3 JBoss JIRA Server 2014-02-24 12:19:00 UTC

Pedro Ruivo <pruivo> updated the status of jira ISPN-4053 to Coding In Progress

Comment 4 Pedro Ruivo 2014-02-25 14:49:32 UTC

Shay, I'm unable to reproduce this in any version. Do you have any logs? 

I created this test [1] and everything seems to work. If you have some sample code that reproduces this issue, I'll be glad to have it.

Comment 5 Pedro Ruivo 2014-02-25 14:50:24 UTC

ops, forgot the link 
[1] https://github.com/pruivo/infinispan/commit/3504baf8225a25f4d185f463e20ab4171387d0b9#diff-08515c048ae2997f4096369f47c420b1R55

Comment 6 Shay Matasaro 2014-02-25 19:13:58 UTC

Pedro, 

this was tested when the repeatable read bz(https://bugzilla.redhat.com/show_bug.cgi?id=1047905) was still not fixed.

Is it possible that fixing one, resolved the other?

The test harness I used was the same for both issues , but on one test I enabled WritSkew , to see if I got the exception.your code looks just like the code I used.

Comment 7 Pedro Ruivo 2014-02-25 19:48:57 UTC

Hi Shay,

yes, probably I fixed without knowing. I'll add the my tests to both to the test suite.

Comment 8 Shay Matasaro 2014-02-25 20:34:02 UTC

great :)

thanks much!

Comment 9 Red Hat Bugzilla 2025-02-10 03:34:44 UTC

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.