Toli, I think this behaviour is standard. We use plain log4j in our processes and log4j reads
the config once at startup.

On the other hand, e.g. the JBoss app server refreshes properties regularly.

Actually, this depends how log4j is used programmatically. I remember some methods / classes in the API
to support this, but at moment I forgot where they are...

So I guess this should be handled inside the SL4J adapter code. Did you check whether they support some
config do enable this?

Cheers, Jörg

Jörg is correct. I think you need to use http://logging.apache.org/log4j/docs/api/org/apache/log4j/PropertyConfigurator.html#configureAndWatch(java.lang.String) to make it reread the property file. I suspect you can just do this first thing in your application.

It should not be QFJ that does this though unless it is optional - otherwise other environments that already do this (eg, JBoss) might not behave as expected.

Cheers,
Brad.

Toli, I agree with Brad's comments. Does that approach sound OK to you?

Hmm, i think we are using conifgureAndWatch in our app ourselves (we use Log4J directly): http://trac.marketcetera.org/trac.fcgi/browser/platform/trunk/core/src/main/java/org/marketcetera/core/LoggerAdapter.java#L41

but it's been over a year since i've touched or looked at the logging code, so maybe there's some weird interplay of how we start the log4j and how QFJ does the same through SLF4J.

but it does sound like something is incorrect in our own setup. i'll investigate a bit more and let you guys know. thanks for the advice.