-
1. Re: Separate Logging for custom actions
stlecho May 27, 2008 8:40 AM (in response to hitsum)Hi,
In my .esb archive I've deployed a log4j.xml file in the following locations: .esb/, .esb/META-INF, .esb/META-INF/classes but JBossESB is still using the default one: conf/jboss-log4j.xml.
Is it possible to have a separate log4j.xml for each .esb archive ?
Regards, Stefan Lecho. -
2. Re: Separate Logging for custom actions
kconner May 30, 2008 7:09 AM (in response to hitsum)It is not something that we have tried but the general advice is still applicable.
See http://wiki.jboss.org/wiki/ScopedLoggingConfig -
3. Re: Separate Logging for custom actions
stlecho May 30, 2008 9:39 AM (in response to hitsum)It would however be nice if we could just deploy a log4j.xml file in the ESB archive and that it gets automagically :o) used when starting the service.
-
4. Re: Separate Logging for custom actions
tfennelly May 31, 2008 3:15 AM (in response to hitsum)Not possible AFAIK and I agree... it's a PITA. I guess the new OSGi based MC will allow this level of control.
-
5. Re: Separate Logging for custom actions
marklittle Jun 1, 2008 7:03 AM (in response to hitsum)Have you tried http://wiki.jboss.org/wiki/Logging?
-
6. Re: Separate Logging for custom actions
kconner Jun 2, 2008 4:24 AM (in response to hitsum)"stlecho" wrote:
It would however be nice if we could just deploy a log4j.xml file in the ESB archive and that it gets automagically :o) used when starting the service.
Please read my previous link, it details how to do this. You have to do a little more than 'just deploy a log4j.xml' though (but not much more). -
7. Re: Separate Logging for custom actions
stlecho Jun 2, 2008 5:56 AM (in response to hitsum)You have to do a little more than 'just deploy a log4j.xml' though (but not much more).
I've used the TCLFilter as explained in http://wiki.jboss.org/wiki/SeparatingApplicationLogs and it works, but ... this means that the jboss-log4j.xml has to be changed at every new deployment.
Why isn't the "packaged log4j.xml" - i.e. the log4j.xml included in the ESB archive is used - approach not supported ? -
8. Re: Separate Logging for custom actions
kconner Jun 2, 2008 6:09 AM (in response to hitsum)This is functionality we are inheriting from the base server (JBoss micro kernel) and is not within our control at present.
You can achieve the same functionality by scoping the deployment and including the log4j jars/config within.