[
https://issues.apache.org/jira/browse/LOGCXX-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thorsten Schöning resolved LOGCXX-359.
--------------------------------------
Resolution: Fixed
I applied the patch from LOGCXX-317.
> Lock order violation
> --------------------
>
> Key: LOGCXX-359
> URL: https://issues.apache.org/jira/browse/LOGCXX-359
> Project: Log4cxx
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.10.0
> Reporter: Stefan Röllin
> Assignee: Curt Arnold
> Priority: Critical
> Attachments: example.cpp, helgrind-report.txt
>
>
> Calling log4cxx::configureAndWatch() results in Logger::mutex being locked
> first, and Hierarchy::mutex being locked nested.
> Calling log4cxx::LogManager::resetConfiguration() results in Hierarchy::mutex
> being locked first, and Logger::mutex being locked nested.
> See also attached example and output from helgrind.
> Similar problem as in issue 317.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
