You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Mikael Ståldal (JIRA)" <ji...@apache.org> on 2017/11/30 19:29:00 UTC
[jira] [Closed] (LOG4J2-2091) Log4j respects the configured
"log4j2.is.webapp" property
[ https://issues.apache.org/jira/browse/LOG4J2-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikael Ståldal closed LOG4J2-2091.
----------------------------------
Released.
> 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
> Assignee: Mikael Ståldal
> Fix For: 2.10.0
>
>
> 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)