Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-4969

Stopping a cache will stop all KeyAffinityServices created for other caches in the cache manager

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 5.2.9.Final, 7.0.1.Final
    • 5.2.8.Final, 6.0.2.Final, 7.0.0.Final
    • Core
    • None

    Description

      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 might be triggered by any cache, 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.

      Attachments

        Activity

          People

            pferraro@redhat.com Paul Ferraro
            pferraro@redhat.com Paul Ferraro
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: