[
https://issues.apache.org/jira/browse/LOG4J2-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866692#comment-13866692
]
Giovanni Mondo commented on LOG4J2-484:
---------------------------------------
It can happen that log is not where I expect because of an error in writing a
path in configuration file, ... and console (or catalina.out with tomcat, ...)
is unavailable or whatever else (the combination of two improbable events that
seems more common than should be :-( ). With a "default" log these problems
are reduced.
I'm sure is not the better way, but it sounds strange that it works for servlet
and not for ServletContextListeners (and probably servlet filters).
> log4j2 and ServletContextListeners
> ----------------------------------
>
> Key: LOG4J2-484
> URL: https://issues.apache.org/jira/browse/LOG4J2-484
> Project: Log4j 2
> Issue Type: Question
> Components: Configurators
> Affects Versions: 2.0-beta9
> Environment: java 1.7.0_11-b21, tomcat-7.0.14
> Reporter: Giovanni Mondo
> Priority: Trivial
> Labels: newbie
> Fix For: 2.0-rc1
>
> Attachments: MavenWeb2.zip
>
>
> Logging configuration is done by two config file:
> WEB-INF/classes/log4j2.xml logging in /tmp/default_MavenWeb.log
> and
>
> /tmp/final_log4j2.xml as log4jConfiguration of a Log4jServletContextListener
> logging in /tmp/MavenWeb.log
>
> Is it possible to log HelloWorldServletContextListener in /tmp/MavenWeb.log
> as HelloWorldServlet does ?
> A minimal maven project with full details can be found in attachment.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
