tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Romain Manni-Bucau <>
Subject Re: Logging configuration in TomEE 1.5.1 with commons-logging and log4j
Date Mon, 28 Jan 2013 10:31:26 GMT
once again log4j uses the config of its classloader.

so you have to put everything (jar + conf) in the app

if you dont manage to do it just create a maven project reproducing the
issue runnable with tomee maven plugin to let us have a look

*Romain Manni-Bucau*
*Twitter: @rmannibucau <>*
*Blog: ***<>
*LinkedIn: ***

2013/1/28 ajaeger <>

> Hi,
> no, putting log4j.xml (or log4j2.xml) + "log4j.jar" in the app is not
> enough.
> We had to put log4j.jar in <TOMEE_HOME>/lib and a log4j.xml in each
> webapp/lib.
> If we configure a class for logging in webapp A with its log4j.xml
> the same class in webapp B also logs to the same logfile  despite different
> configuration in this log4j.xml
> The log4j.xml which is changed last "wins".
> We found that you can only have one global log4j.xml for all apps.
> Is this correct?
> Is there no way to configure logging separately for each webapp?
> Is there a way to enable child-first class loading instead of parent-first
> class loading in TomEE?
> Regards
> Andreas
> --
> View this message in context:
> Sent from the OpenEJB User mailing list archive at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message