[jboss-jira] [JBoss JIRA] (AS7-5255) Deployed log4j.properties does not affect non log4j logging systems
[
https://issues.jboss.org/browse/AS7-5255?page=com.atlassian.jira.plugin.s...
]
James Perkins commented on AS7-5255:
------------------------------------
How could I forget :-). I need to look at the code and work it through my head. My gut was
that it needed to pass through the log4j log manager, which in turn just uses JBoss Log
Manager. That's where I need to think of the flow. It does seem it should work
though.
Regardless in this particular case it does seem {{logging.properties}} would be a better
approach. Not need to involve log4j if it's not using any kind of special appender.
Deployed log4j.properties does not affect non log4j logging systems
-------------------------------------------------------------------
Key: AS7-5255
URL: https://issues.jboss.org/browse/AS7-5255
Project: Application Server 7
Issue Type: Bug
Components: Logging
Affects Versions: 7.1.2.Final (EAP)
Reporter: Patrick Ruckstuhl
Assignee: James Perkins
If I create the file
my.ear/META-INF/log4j.properties
with
log4j.rootLogger=DEBUG, FA
log4j.appender.FA=org.apache.log4j.FileAppender
log4j.appender.FA.File=/tmp/my.log
log4j.appender.FA.layout=org.apache.log4j.PatternLayout
log4j.appender.FA.layout.ConversionPattern= %-4r [%t] %-5p %c %x - %m%n
this results in nothing in the server.log and an empty /tmp/my.log
but if I create a
my.ear/META-INF/logging.properties
this results in everything beeing logged to /tmp/my.log
We're using SLF4J in our application and also using a library that uses
COMMONS-LOGGING
I also did a test with doing an additional log statement using the log4j api directly and
this one (and only this one) did get logged to /tmp/my.log
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira