[ https://issues.apache.org/jira/browse/LOG4J2-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16318255#comment-16318255 ]
Romain Manni-Bucau commented on LOG4J2-2171: -------------------------------------------- done at https://github.com/apache/logging-log4j2/pull/140 > Log4j2 is not embeddable due to its system classloader usage > ------------------------------------------------------------ > > Key: LOG4J2-2171 > URL: https://issues.apache.org/jira/browse/LOG4J2-2171 > Project: Log4j 2 > Issue Type: Bug > Reporter: Romain Manni-Bucau > > 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 -- This message was sent by Atlassian JIRA (v6.4.14#64029)