You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jcs-dev@jakarta.apache.org by "Aaron Smuts (JIRA)" <ji...@apache.org> on 2007/03/19 03:30:10 UTC
[jira] Resolved: (JCS-21) JCS has inconsistent locking of shared
data
[ https://issues.apache.org/jira/browse/JCS-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aaron Smuts resolved JCS-21.
----------------------------
Resolution: Fixed
I applied all the changes except for some private method changes and the optimization method on the indexed disk cache.
> 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