Bug 1024934

Summary: 1PC can cause a window of inconsistency with L1 invalidation
Product: [JBoss] JBoss Data Grid 6 Reporter: Martin Gencur <mgencur>
Component: unspecifiedAssignee: Tristan Tarrant <ttarrant>
Status: VERIFIED --- QA Contact: Martin Gencur <mgencur>
Severity: high Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: jdg-bugs
Target Milestone: ER4   
Target Release: 6.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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:
Bug Depends On:    
Bug Blocks: 1017190    

Description Martin Gencur 2013-10-30 15:28:32 UTC

Comment 2 JBoss JIRA Server 2013-11-05 14:36:04 UTC
William Burns <wburns> updated the status of jira ISPN-3518 to Coding In Progress

Comment 3 JBoss JIRA Server 2013-12-10 10:30:30 UTC
Radim Vansa <rvansa> made a comment on jira ISPN-3518

I know it's already fixed, but is it really a bug? The described scenario does not break the serializability property of the transactions - the outcome is the same as if tx2 was executed before tx1. Could you describe the scenario where it does break some expected property?