You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2010/04/11 23:21:40 UTC
[jira] Resolved: (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 ]
Felix Meschberger resolved SLING-1326.
--------------------------------------
Resolution: Fixed
No further issues seem to have occurred. So I think we can resolve this issue fixed.
> 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.0.8
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira