Aleksandr Slepnev

I caught this bug also and decided to rollback mosquitto version to 1.4.10, but this solutions isn't good I think. It's better to resolve the problem from **iotjs** side.

@leventov @wilx I have tested the patches from branch [master-make-hashtable-mutex-rw-lock](https://github.com/wilx/log4cplus/tree/master-make-hashtable-mutex-rw-lock), as a result, the main thread froze on infinity waiting. ``` Thread 1 (Thread 0x7ffff675ac80 (LWP 31095)): #0 futex_wait_cancelable (private=0,...

I have found the root cause of problem above: if your application tries to reset the configuration by the following method, you will get a dead lock. ``` log4cplus::HierarchyLocker lock(log4cplus::Logger::getDefaultHierarchy());...

> There we can use C++20 features and drop the poor man's shared mutex in favour of standard C++ shared mutex. Yes, agree with you. Also, I want to mention...

Any updates?