[
https://issues.apache.org/jira/browse/LOG4J2-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16258604#comment-16258604
]
ASF GitHub Bot commented on LOG4J2-2110:
----------------------------------------
Github user thomasbeauvais commented on the issue:
https://github.com/apache/logging-log4j2/pull/128
I have fixed the whitespace.
What can I do to help you figure out why it wasn't being initialized? A
colleague and myself spent a couple hours debugging to find this. It very
strange behavior and seems to have been there for quite sometime. We have added
this exact fix, and now everything is started and stopped properly each time.
Out problem was that we are starting up a few of resources. Without this
fix, we noticed leaks on redeployment. The stop was never call since the
{{servletContext}} in the {{Log4jServletContextListener}} is always {{null}} no
matter what you do.
> Log4jServletContextListener skips initialization and thusly never calls stop()
> ------------------------------------------------------------------------------
>
> Key: LOG4J2-2110
> URL: https://issues.apache.org/jira/browse/LOG4J2-2110
> Project: Log4j 2
> Issue Type: Bug
> Components: Web/Servlet
> Affects Versions: 2.8, 2.8.1, 2.8.2, 2.9.0, 2.9.1
> Reporter: Thomas Beauvais
> Priority: Critical
>
> {{Log4jServletContextListener}} is not working in Tomcat 8 or 8.5 as it's
> never initialized.
> The {{contextInitialized}} is never called and thus it never sets the
> {{servletContext}}.
> This is checked when a {{servletContext}} is destroyed and ignored every time.
> The outcome, is that our customer appenders are never stopped leading to
> resource leaks.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
