You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shindig.apache.org by "Stanton Sievers (JIRA)" <ji...@apache.org> on 2013/09/01 15:07:51 UTC
[jira] [Updated] (SHINDIG-1931) EhCache provider always uses a
singleton cache manager, even if it is the wrong one
[ https://issues.apache.org/jira/browse/SHINDIG-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stanton Sievers updated SHINDIG-1931:
-------------------------------------
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
> EhCache provider always uses a singleton cache manager, even if it is the wrong one
> -----------------------------------------------------------------------------------
>
> Key: SHINDIG-1931
> URL: https://issues.apache.org/jira/browse/SHINDIG-1931
> Project: Shindig
> Issue Type: Bug
> Components: Java
> Affects Versions: 2.5.0
> Reporter: Stanton Sievers
> Assignee: Stanton Sievers
> Fix For: 2.5.0-update1
>
>
> 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
--
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