logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Seweryn Habdank-Wojewodzki (JIRA)" <j...@apache.org>
Subject [jira] [Created] (LOG4J2-1841) Problems with consequences after LOG4J2-248
Date Thu, 09 Mar 2017 07:02:38 GMT
Seweryn Habdank-Wojewodzki created LOG4J2-1841:

             Summary: Problems with consequences after LOG4J2-248
                 Key: LOG4J2-1841
                 URL: https://issues.apache.org/jira/browse/LOG4J2-1841
             Project: Log4j 2
          Issue Type: Bug
          Components: Boot
    Affects Versions: 2.8
         Environment: Linux, Tomcat, WebApps
            Reporter: Seweryn Habdank-Wojewodzki

Situation till Log4j v. 2.5:

1. One instance of Tomcat WITHOUT definition of the log4j.configurationFile variable.
2. Several WARs deployed on within this concrete instance of the Tomcat.
3. Every WAR internally contains own log4j2.xml file. So every Log4j instance, which is global
for the WebApp, but local for the Tomcat, will search and use configuration in own class path.

Works in the way that every Web-App got own Log4j config and will operate according to own
definitions (appenders, layouts, loggers).

In the Log4j v. 2.6 and later in the same setup we are observing the following:

Log4j in the applications are reporting problem that config file (log4j2.xml) is not visible.
Thus we got message, that Log4j will switch to backup mode which will write only ERRORs in
the console.

We debuged that issue and found that change made in:
seems to be the main reason.

We cannot asses if this change was made only with respect to some PMD warning or it has as
well some design considerations in background.

The consequence is that Tomcat instance shall define log4j.configurationFile variable, but
also it means ALL WebApps will use one single configuration, what makes definitely problem,
as all WebApps providers must argee on ONE confing including appenders configuration, message
Layout and so on.

Consider this report and provide solution (or workaround) for the given system setup, please

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message