[infinispan-issues] [JBoss JIRA] (ISPN-2903) Manual eviction should not delete entry from cache store

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on ISPN-2903:
-----------------------------------------------

Scott Mumford <smumford at redhat.com> made a comment on [bug 900549|https://bugzilla.redhat.com/show_bug.cgi?id=900549]

Since this bug now seems to be fixed, the release note text above is out of date.

Is it possible to get an executive summary of what was causing this bug (beyond 'failover') and how it was resolved for the updated note.

Thanks in advance.
                
> Manual eviction should not delete entry from cache store
> --------------------------------------------------------
>
>                 Key: ISPN-2903
>                 URL: https://issues.jboss.org/browse/ISPN-2903
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Eviction
>    Affects Versions: 5.2.3.Final
>            Reporter: Paul Ferraro
>            Assignee: Galder Zamarreño
>            Priority: Critical
>              Labels: 5.2.x, jdg6
>             Fix For: 5.2.5.Final, 5.3.0.Alpha1, 5.3.0.Final
>
>         Attachments: AtomicMapServlet.java, AtomicMapTestCase.java, server.log, server.log
>
>
> Here's the scenario:
> Given 2 nodes with REPL_SYNC cache with passivating cache store (e.g. default web cache in AS7).
> 1. Create cache entry containing atomic map with 2 map entries on node1.
> 2. Passivate that cache entry on node2 via manual evict.
> 3. Modify 1 of the atomic map entries within the cache entry on node1.
> 4. Lookup atomic map on node2.  It only contains 1 map entry - the map entry modified in step 3.  The other map entry is lost.
> It's a side effect of ISPN-2384, where some changes were made to tighten the passivation/activation scenarios, but it did not cover manual eviction calls.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira