t: Re: Rehashing question about consequences of using
> configureAndWatch in a servlet
>
> Karr, David wrote:
>
>
>
> > 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
Karr, David wrote:
> 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 re
I've googled the many discussions about the impact of using
"configureAndWatch()" in a servlet. The Log4J FAQ says it is "unsafe"
to use this in a J2EE application because of the nature of how this
works. Discussion about this has been going on for a very long time (in
internet time).
I'd like t
