Separate Logging for custom actions

[hitsum]

Hi All,

I want to configure log4j with my custom actions. I want the logging of my actions to be diverted to a separate log file other than server.log

Is it possible? How do do so?

Thank you

hitsum

[stlecho]

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.

[kconner]

It is not something that we have tried but the general advice is still applicable.

See http://wiki.jboss.org/wiki/ScopedLoggingConfig

[stlecho]

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.

[tfennelly]

Not possible AFAIK and I agree... it's a PITA. I guess the new OSGi based MC will allow this level of control.

[marklittle]

Have you tried http://wiki.jboss.org/wiki/Logging?

[kconner]

"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).

[stlecho]

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 ?

[kconner]

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.