Could you clarify a bit. I am not quite sure what to make of your answer,
"Nope" and "Log4j is thread safe" seem a bit contradictory. "Nope" could
mean problems are possible and "thread safe" could mean they are not.
I suppose that being thread safe (which I was aware of) does not preclude
problems when the log4j configuration has been reset.
Thanks
Rick Hansen
>
> Nope. Log4j is thread safe. Ceki
>
> At 16:56 05.06.2001 -0500, you wrote:
> >I am using log4J in a J2EE environment and would like to
> reload the log4j
> >configuration if the config file changes. I know I can use
> FileWatchdog and
> >doOnChange(). But I am wondering whether this is safe?
> Between calling
> >resetConfiguration() and doConfigure() is there any
> guarantee that some
> >other thread won't try to log and cause an error?
> >
> >Rick Hansen
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
