You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2019/06/23 08:16:00 UTC

[jira] [Resolved] (LOG4J2-871) Add support for using Log4j as a global Tomcat library.

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

Ralph Goers resolved LOG4J2-871.
--------------------------------
    Resolution: Fixed

Log4j has a log4j-appserver module that supports this with Tomcat 8.5

> Add support for using Log4j as a global Tomcat library.
> -------------------------------------------------------
>
>                 Key: LOG4J2-871
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-871
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: Core, Web/Servlet
>    Affects Versions: 2.0.2, 2.1
>            Reporter: Matt Sicker
>            Priority: Major
>
> I would like to be able to use log4j-api and log4j-core in my global Tomcat lib directory and have it both integrate with JULI (which the log4j-jul module may help, though there could be more work involved) as well as properly integrate with any shutdown logic Tomcat provides to delay shutdown of the logging system until the very end.
> If possible, it would be great if this could either be generic enough or extensible enough to allow the same for Jetty, too.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)