You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Matt Sicker (JIRA)" <ji...@apache.org> on 2018/04/09 16:00:00 UTC

[jira] [Assigned] (LOG4J2-2171) Log4j2 is not embeddable due to its system classloader usage

     [ https://issues.apache.org/jira/browse/LOG4J2-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Sicker reassigned LOG4J2-2171:
-----------------------------------

    Assignee: Matt Sicker

> 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
>            Assignee: Matt Sicker
>            Priority: Major
>             Fix For: 3.0.0
>
>
> 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
(v7.6.3#76005)