You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/11/04 07:51:27 UTC

[jira] [Issue Comment Deleted] (SLING-3793) Field in MimeTypeServiceImpl must be declared volatile

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

Carsten Ziegeler updated SLING-3793:
------------------------------------
    Comment: was deleted

(was: The field is holding a dynamic reference - so this field can change over time. Whenever the log service gets available it is set to the service instance, when the log service gets unavailable (e.g. if the log bundle is updated) it gets set to null. Volatile is required in this case to make this change visible not only to the thread changing the field, but to all threads using the mime type service)

> Field in MimeTypeServiceImpl must be declared volatile
> ------------------------------------------------------
>
>                 Key: SLING-3793
>                 URL: https://issues.apache.org/jira/browse/SLING-3793
>             Project: Sling
>          Issue Type: Bug
>          Components: Commons
>    Affects Versions: Commons Mime 2.1.4
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Commons Mime 2.1.6
>
>
> The field logService must be declared as volatile



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)