[
https://issues.apache.org/jira/browse/LOG4J2-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16220677#comment-16220677
]
ASF GitHub Bot commented on LOG4J2-2091:
----------------------------------------
Github user cakofony commented on the issue:
https://github.com/apache/logging-log4j2/pull/120
Hi @jvz, thanks for the quick reply!
I've added a jira ticket, but I'm not sure the best way to add real tests
for this given how this is configured as static state. Any chance you could
point me in the right direction?
> Log4j respects the configured "log4j2.is.webapp" property
> ---------------------------------------------------------
>
> Key: LOG4J2-2091
> URL: https://issues.apache.org/jira/browse/LOG4J2-2091
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.9.1
> Reporter: Carter Douglas Kozak
>
> When running an application with an embedded servlet container, the
> configuration should be able to enable shutdown hook registration, and avoid
> the "Log4j appears to be running in a Servlet environment, but there's no
> log4j-web module" warning.
> Steps to reproduce:
> 1. configure log4j2.is.webapp = false
> 2. Start application with a dependency on the servlet-api
> 3. "Log4j appears to be running in a Servlet environment, but there's no
> log4j-web module available." warning is logged
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
