Bug 1388562 - Expiration is not applied to a repeatable read entry that was read as null prior
Summary: Expiration is not applied to a repeatable read entry that was read as null prior
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Embedded
Version: 6.6.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: DR1
: 6.6.2
Assignee: William Burns
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks: 1374440
TreeView+ depends on / blocked
 
Reported: 2016-10-25 16:27 UTC by William Burns
Modified: 2020-01-17 16:05 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug

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


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-5699 0 Major Resolved Simplify entry wrapping 2017-07-24 21:29:21 UTC

Internal Links: 1394926

Description William Burns 2016-10-25 16:27:48 UTC 
Description of problem:

The expiration metadata is not applied to a newly created entry that was read in the same transaction as a null.

Issue was found in https://access.redhat.com/support/cases/#/case/01715604

Also just for information purposes this issue was fixed in 8.1.x of ISPN and is only present in 8.0.x.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 William Burns 2016-10-25 17:43:54 UTC 
https://issues.jboss.org/browse/ISPN-5699 was the issue that fixed this.
Comment 3 William Burns 2016-10-25 17:45:57 UTC 
PR: https://github.com/infinispan/jdg/pull/1029
Note You need to log in before you can comment on or make changes to this bug.