Project

General

Profile

Bug #2193

Log4j Configuration not effective once more....

Added by Henning Blohm 4 days ago. Updated 2 days ago.

Status:
Feedback
Priority:
High
Assignee:
-
Category:
-
Target version:
Start date:
15.04.2025
Due date:
% Done:

0%

Estimated time:
origin:

Description

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.

Acceptance Criteria

  • The fix of #2166 is applied again
  • The log context configured is held onto.

Related issues

Related to z2-Environment - Bug #2166: Log4j2 configuration from environment not effective.Resolved30.01.2024Henning Blohm

Actions

Also available in: Atom PDF