[
https://issues.apache.org/jira/browse/QPID-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463538
]
Rupert Smith commented on QPID-147:
-----------------------------------
Yes, because on start up log4j loads log4j.properties by default. Even though
the XMLDomConfigurator is called with a log4j.xml file that it appears to
process, it does not replace the config already loaded from the .properties
file.
I think, in general all log4j.properties files should be ditched and use xml
configs instead to help avoid this sort of problem.
Here's a patch for the maven build to exclude the log4j.properties from the
distribution jars.
> Remove log4j.properties from BAU distribution
> ---------------------------------------------
>
> Key: QPID-147
> URL: https://issues.apache.org/jira/browse/QPID-147
> Project: Qpid
> Issue Type: Improvement
> Components: Maven build system
> Reporter: Marnie McCormack
> Priority: Minor
> Fix For: M2
>
> Attachments: Qpid-147.diff
>
>
> Users have commented that having a log4.properties in the distributed jars is
> an issue since it can often cause havoc with their own logging. Should ship
> the log4.properties separately.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
