Lock order violation

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.