You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-user@logging.apache.org by Daniel Serodio <ds...@pucsp.br> on 2006/05/25 15:45:03 UTC
Re: Rehashing question about consequences of using configureAndWatch
in a servlet
Karr, David wrote:
<snip>
> I would guess the way to rectify this would be to write your own loop in
> a thread that watches the log4j.xml file, with a timeout on each
> iteration, which checks a static flag that could be set in the
> "destroy()" method.
>
> If "configureAndWatch()" in a servlet is really unsafe, I find it hard
> to believe someone hasn't written a reusable replacement for
> "configureAndWatch()" that can exit on command.
David, have you found a solution for this? I was just about to use
configureAndWatch() when I saw this post.
Thanks,
Daniel Serodio
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org