You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2014/08/06 10:25:14 UTC

[jira] [Resolved] (SLING-3824) Unneeded volatile fields in StatisticsImpl and TopicStatisticsImpl

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

Robert Munteanu resolved SLING-3824.
------------------------------------

       Resolution: Fixed
    Fix Version/s: Event 3.3.14

Fixed in https://svn.apache.org/viewvc?view=revision&revision=1616122

> Unneeded volatile fields in StatisticsImpl and TopicStatisticsImpl
> ------------------------------------------------------------------
>
>                 Key: SLING-3824
>                 URL: https://issues.apache.org/jira/browse/SLING-3824
>             Project: Sling
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: Event 3.3.12
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>             Fix For: Event 3.3.14
>
>
> The findbugs violations report at https://analysis.apache.org/drilldown/issues/35893?rids[]=150490&rule=findbugs%3AVO_VOLATILE_INCREMENT&rule_sev=CRITICAL&severity=CRITICAL# indicates that these classes have volatile fields which are incremented with the postfix increment operator. This operation is not guaranteed to be atomic, therefore it is unsafe for volatile fields.
> However, these fields do not need to be volatile since they are only accessed from synchronized methods.



--
This message was sent by Atlassian JIRA
(v6.2#6252)