Mailing-List: contact jcs-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "JCS Developers List" <jcs-dev@jakarta.apache.org>
Message-ID: <17501346.1174231989567.JavaMail.jira@brutus>
Date: Sun, 18 Mar 2007 08:33:09 -0700 (PDT)
From: "Michael Stevens (JIRA)" <jira@apache.org>
To: jcs-dev@jakarta.apache.org
Subject: [jira] Updated: (JCS-21) JCS has inconsistent locking of shared
 data
In-Reply-To: <13364313.1174231989274.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Michael Stevens updated JCS-21:
-------------------------------

    Attachment: locking.diff

patch to jcs locking code

> JCS has inconsistent locking of shared data
> -------------------------------------------
>
>                 Key: JCS-21
>                 URL: https://issues.apache.org/jira/browse/JCS-21
>             Project: JCS
>          Issue Type: Bug
>    Affects Versions: jcs-1.2.7.9.2
>            Reporter: Michael Stevens
>         Assigned To: Aaron Smuts
>         Attachments: locking.diff
>
>
> I've been looking at the trunk JCS code with findbugs (http://findbugs.sf.net/).
> One of the things it does is warn when data is inconsistently synchronized - ie when it is sometimes referenced inside a synchronized block and sometimes not. This is not threadsafe - one thread may read old or inconsistent data.
> I've patched all the places findbugs complains about by adding appropriate synchronized() blocks.
> I suspect this change may require some discussion :)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org