[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jakarta-commons-dev
Subject:    [jira] [Resolved] (JCS-116) CompositeCacheManager is thread-hostile
From:       "Thomas Vandahl (JIRA)" <jira () apache ! org>
Date:       2016-01-30 15:25:39
Message-ID: JIRA.12707151.1396953171000.257345.1454167539798 () Atlassian ! JIRA
[Download RAW message or body]


     [ 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)


[prev in list] [next in list] [prev in thread] [next in thread]