Uploaded image for project: 'Shindig'
  1. Shindig
  2. SHINDIG-1931

EhCache provider always uses a singleton cache manager, even if it is the wrong one

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.5.0
    • 2.5.1, 2.5.0-update1
    • Java
    • None

    Description

      Reported on the dev list[1]. The issue is that the CacheManager.create(Configuration) APIs will always use the same singleton, regardless of whether the provided Configuration defines a cache manager of a different name then the existing singleton. We should use the CacheManager.newInstance(Configuration) APIs, as this will use a singleton per cache manager name. This will keep us from stomping on other cache managers that exist in the environment.

      [1] http://markmail.org/message/4adopzvvi3ltv7yq?q=Shindig+list:org.apache.shindig.dev+order:date-backward&page=1

      Attachments

        Activity

          People

            ssievers Stanton Sievers
            ssievers Stanton Sievers
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment