Yes I know. But it might be better not to use the configureAndWatch method but instead use an own mechanism which I can change via JMX. I have to have a look at it first. You could give me a hint where servicmix does initialise the log4j system at the moment but I can also have a look at it. What do you think? Would you use the configureAndWatch mechanism? I would like to change the delay time at runtime and use a TimerTask to schedule this stuff. Then you could also stop scheduling via JMX and so on.
Guillaume Nodet wrote: > See http://logging.apache.org/log4j/docs/faq.html#3.6 > I don't think there is much code to write... > > On 10/20/06, Thomas TERMIN <[EMAIL PROTECTED]> wrote: >> Sorry I did not mean a servicemix component. I use allways the word >> component ;-) since I started working with servicemix. What you said is >> exactly what I meant. So I will have a look on it! >> >> Thanks, >> Thomas >> >> Guillaume Nodet wrote: >> > I would rather use a ServiceMix service instead of >> > a component, as this is more related to management / >> > configuration than a component if I understand you >> > correctly. ... and use a timer to reload the log4j config. >> > But iirc, log4j already has this feature, we just need to >> > enable it. >> > >> > On 10/20/06, Thomas TERMIN <[EMAIL PROTECTED]> wrote: >> >> Hello Guillaume, >> >> >> >> We would need a log4j Component where you can change the debug >> level at >> >> runtime. I would implement a MBean which initialise the log4j >> system at >> >> startup and also have a scheduler which looks if the log4j.xml has >> >> changed and then reinitialise the log4j system. >> >> >> >> If I would provide you a patch would you accept this in servicemix? >> >> >> >> Cheers, >> >> Thomas Termin >> >> >> > >> > >> >> > >
