commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Vandahl (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (JCS-116) CompositeCacheManager is thread-hostile
Date Sat, 30 Jan 2016 15:25:39 GMT

     [ https://issues.apache.org/jira/browse/JCS-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thomas Vandahl resolved JCS-116.
--------------------------------
    Resolution: Fixed

Attempted a fix. Please review.

> CompositeCacheManager is thread-hostile
> ---------------------------------------
>
>                 Key: JCS-116
>                 URL: https://issues.apache.org/jira/browse/JCS-116
>             Project: Commons JCS
>          Issue Type: Bug
>            Reporter: Sebb
>            Assignee: Thomas Vandahl
>            Priority: Blocker
>             Fix For: jcs-2.0-beta-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)

Mime
View raw message