[ 
https://issues.apache.org/jira/browse/LOG4J2-870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Remko Popma closed LOG4J2-870.
------------------------------
    Resolution: Not a Problem

Thanks for providing your configuration. Now I understand what happened.

Your application logs at DEBUG level, but the root logger filtered out all 
events that were not at least INFO, so no events were sent to the appenders.

After modifying {{<root level="info">}} to {{<root level="debug">}}, the events 
that your application logs at DEBUG level are now sent to the appenders.

(Note that if your application logs anything at TRACE level it will not appear 
in the logs. For that you need to change both the root level filtering and the 
filter level on the appender-ref(s).)

> log4j2 with servlet 3.0 container in WAS8.5 not working
> -------------------------------------------------------
>
>                 Key: LOG4J2-870
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-870
>             Project: Log4j 2
>          Issue Type: Question
>          Components: log4j 1.2 emulation
>         Environment: Windows 7, WAS8.5, Java1.6
>            Reporter: Sudhakar
>            Priority: Blocker
>         Attachments: log4j1.png, log4j2.png, log4j3.png, log4j4.png
>
>
> Trying to setup new J2EE project on WAS8.5 using latest Log4J2 jar files. 
> When I run a test servlet, logfiles are not geting created and writing the 
> log.
> http://stackoverflow.com/questions/26164572/log4j2-with-servlet-3-0-container-in-was8-5-not-working
> 1. Log4J2.xml is placed under WEB-INF/classes
> 2.Log4j-api-2.0.2.jar, log4j-core-2.0.2,log4j-web-2.0.2 inluded in the 
> classpath
> if I run DemoLog4J class with main method, I am able to see console and 
> logfiles are written without system property for log4J2.xml location.
>  Please help. Thanks!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to