[infinispan-issues] [JBoss JIRA] (ISPN-4969) Stopping a cache will stop all KeyAffinityServices created for other caches in the cache manager

Paul Ferraro (JIRA) issues at jboss.org
Wed Nov 12 03:02:10 EST 2014


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

Paul Ferraro commented on ISPN-4969:
------------------------------------

This requires fixes for the following branches:
 * 7.0.x, for WildFly 9
 * 6.0.x, for WildFly 8.2
 * 5.2.x, for EAP 6.4

> Stopping a cache will stop all KeyAffinityServices created for other caches in the cache manager
> ------------------------------------------------------------------------------------------------
>
>                 Key: ISPN-4969
>                 URL: https://issues.jboss.org/browse/ISPN-4969
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 5.2.8.Final, 6.0.2.Final, 7.0.0.Final
>            Reporter: Paul Ferraro
>            Assignee: Paul Ferraro
>            Priority: Blocker
>             Fix For: 7.0.1.Final
>
>
> We've had several reports in the WildFly forums of application runtime failures following undeployment of a separate application.
> WF creates a cache instance for each web application within the same cache container.  However, KeyAffinityServiceImpl registers a cache manager listener that calls stop() on a @CacheStoppedEvent.  However, this event is triggered by any cache stop, not necessarily the cache with to which the KeyAffinityService is associated.
> The KeyAffinityServiceImpl.handleCacheStopped(CacheStoppedEvent) should only call stop() if the event.getCacheName() equals the name of the cache to which the affinity service is associated.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)


More information about the infinispan-issues mailing list