[
https://issues.apache.org/jira/browse/LOG4J2-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16258658#comment-16258658
]
Ralph Goers edited comment on LOG4J2-2110 at 11/19/17 10:52 PM:
----------------------------------------------------------------
If Log4jServletContainerInitializer's onStartup method is being called with a
null servletContext then that is definitely a bug in Tomcat and should be
reported to them to be fixed. It also should be causing a NullPointerException
in the onStartup method, which you didn't mention. Furthermore, even your fix
wouldn't work because it is passing the servletContext passed to onStartup to
the ServletContextListener. I suspect you are trying to say that the
ServletContext is not in the ServletContextEvent, but that would also be a bug
in Tomcat and would need to be reported to them.
Again, please provide a sample web app that demonstrates the problem.
was (Author: [email protected]):
If Log4jServletContainerInitializer's onStartup method is being called with a
null servletContext then that is definitely a bug in Tomcat and should be
reported to them to be fixed. It also should be causing a NullPointerException
in the onStartup method, which you didn't mention.
Again, please provide a sample web app that demonstrates the problem.
> 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)
