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 2010/12/20 15:55:02 UTC

[jira] Closed: (SLING-1326) LogConfigManager: Access to internal configuration maps is not thread-safe

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

Carsten Ziegeler closed SLING-1326.
-----------------------------------


> LogConfigManager: Access to internal configuration maps is not thread-safe
> --------------------------------------------------------------------------
>
>                 Key: SLING-1326
>                 URL: https://issues.apache.org/jira/browse/SLING-1326
>             Project: Sling
>          Issue Type: Bug
>          Components: Commons
>    Affects Versions: Commons Log 2.0.6
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: Commons Log 2.1.0
>
>
> The LogConfigManager class has a number of maps to internally manage configurations and writers and logger categories. Access to these maps is not thread-safe and might lead to endless loops if maps get corrupted.
> To fix issue, it would probably be easiest to replace the HashMap obejdcts by ConcurrentHashMap objects.

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