[
https://issues.jboss.org/browse/ISPN-2903?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on ISPN-2903:
-----------------------------------------------
Jitka Kudrnacova <jkudrnac(a)redhat.com> made a comment on [bug
900549|https://bugzilla.redhat.com/show_bug.cgi?id=900549]
I have tested this issue with ER6 and ISPN 5.2.6.Final (taken from BZ 956988, comment 36)
and the issue is still present.
We are still seeing the NPE and we are still seeing BZ 901164 (lost sessions after
failover).
For the testing, I have chosen scenario REPL_SYNC and _graceful_ shutdown.
Looking at the test results, it looks like some of the NPE's (and the consequence
901164) were eliminated by the ISPN upgrade, but most likely there is another cause of
these NPEs that was not discovered and fixed by the ISPN upgrade.
@Rado, please elaborate on your comment on
https://github.com/jbossas/jboss-eap/pull/122 :
the pull 122 was made obsolete by the ISPN upgrade? Brian is asking the same thing on the
pull request discussion.
Link to job:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-http...
Some statistics on the exception numbers:
client side:
ER5: 36478 occurences of 900549
(
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-http...)
ER6 with ISPN 5.2.6.Final: 6370 occurences of 900549
(
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-http...)
server side:
ER5: 18241 occurences of 900549
(
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-http...)
ER6 with ISPN 5.2.6.Final: 3185 of 900549
(
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-http...)
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