[infinispan-issues] [JBoss JIRA] (ISPN-9511) Expired event is not raised when modifying an expired entry

[William Burns (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-9511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635241#comment-13635241 ] 

William Burns edited comment on ISPN-9511 at 9/18/18 12:57 PM:
---------------------------------------------------------------

It looks like this was a bug in https://github.com/infinispan/infinispan/commit/14afdf555b826d78622a534e50fcd84eded7602e#diff-182863b563ea048f2b8e7a9ea42927faR1851
We need to just set the value if the listener using storage format only. This prevents the extra serialization.

And now that the remote listeners all use storage format, this test found it.


was (Author: william.burns):
It looks like this was a bug in https://github.com/infinispan/infinispan/commit/14afdf555b826d78622a534e50fcd84eded7602e#diff-182863b563ea048f2b8e7a9ea42927faR1851
We need to just set the value if the listener using storage format only. This prevents the extra serialization.

> Expired event is not raised when modifying an expired entry
> -----------------------------------------------------------
>
>                 Key: ISPN-9511
>                 URL: https://issues.jboss.org/browse/ISPN-9511
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Listeners
>    Affects Versions: 9.3.3.Final
>            Reporter: William Burns
>            Assignee: William Burns
>             Fix For: 9.4.0.Final
>
>
> Due to the old way of implementing remove expired for lifespan, we didn't raise an expired event when writing to an entry. This was mostly to cause circular dependencies. But with the new remove expired max idle changes, this is now possible.
> Without this change listeners can be in an inconsistent state, possibly, as the following could happen:
> 1. Entry is created
> 2. Listener is notified of creation
> 3. Entry expires (no event yet)
> 4. Entry is written to (created)
> 5. Listener is notified of creation.
> In this case there is no intermediate state where the listener thought there was no entry. This also becomes problematic if you are listening only for events that don't include create.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)