[jira] [Updated] (JCS-116) CompositeCacheManager is thread-hostile
[ https://issues.apache.org/jira/browse/JCS-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Vandahl updated JCS-116: --- Fix Version/s: jcs-2.0.0 > CompositeCacheManager is thread-hostile > --- > > Key: JCS-116 > URL: https://issues.apache.org/jira/browse/JCS-116 > Project: Commons JCS > Issue Type: Bug >Reporter: Sebb >Priority: Blocker > Fix For: jcs-2.0.0 > > > The CompositeCacheManager class is a singleton. However it is not immutable, > so is inherently thread-hostile. > The class does take some steps to prevent reconfiguration, but it still > allows changes to variables such as defaultCacheAttr that affect instance > methods such as getCache(String) > This makes it very easy to accidentally affect other threads. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (JCS-116) CompositeCacheManager is thread-hostile
[ https://issues.apache.org/jira/browse/JCS-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Vandahl updated JCS-116: --- Fix Version/s: (was: jcs-2.0-alpha-1) jcs-2.0-alpha-2 > CompositeCacheManager is thread-hostile > --- > > Key: JCS-116 > URL: https://issues.apache.org/jira/browse/JCS-116 > Project: Commons JCS > Issue Type: Bug >Reporter: Sebb >Priority: Blocker > Fix For: jcs-2.0-alpha-2 > > > The CompositeCacheManager class is a singleton. However it is not immutable, > so is inherently thread-hostile. > The class does take some steps to prevent reconfiguration, but it still > allows changes to variables such as defaultCacheAttr that affect instance > methods such as getCache(String) > This makes it very easy to accidentally affect other threads. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
