Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Hi guys,
in several places, log4j2 enforces the system classloader to be used. I have a case where I isolate a classloader from the app which can have log4j2 and I don't want any leakage between both classloaders.
This is current not possible. Can we have at least an option to skip this classloader and only use the tccl one?
For reference: org.apache.logging.log4j.util.LoaderUtil#getClassLoaders, org.apache.logging.log4j.util.LoaderUtil#findUrlResources, etc... are the places making it not working