Bug #2193
Updated by Henning Blohm 2 days ago
As observed at TK: Due to a merge, the fix of #2166 got lost again. But there is more. As Log4j retrieves log contexts via walking up the class loader hierarchy (See @org.apache.logging.log4j.core.selector.ClassLoaderContextSelector.locateContext(ClassLoader, Entry<String, Object>, URI)@) using a weak reference value map, in order to make sure that our "system classloader" context is preserved we must make sure that it does not get collected. h2. Acceptance Criteria * The fix of #2166 is applied again * The log context configured is held onto.