[
https://issues.apache.org/jira/browse/LOG4J2-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16224140#comment-16224140
]
ASF subversion and git services commented on LOG4J2-2091:
---------------------------------------------------------
Commit b59819e47c06d9e928df7e90bdb75189fd9ce306 in logging-log4j2's branch
refs/heads/master from [~ckozak]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=b59819e ]
LOG4J2-2091: Respect the configured "log4j2.is.webapp" property
Some applications run embedded servlet containers sharing
a single logging context from the root application.
> 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)
