Thank you for your reply, Ceki.
First, the rolling appenders have been rewritten. See o.a.l.rolling package in log4j cvs.
I will refer to the cvs sources (so far I was based on the sources in the jar). Do the re-written appenders address this issue? I'll probably self-answer that by reading the sources.
Second, it is not good practice to hide threads within appenders.
What is the reason bahind this? The thread used is a daemon thread, so it will not hang the system... is it because of using up an additional thread per instance? In all situations, a common timer can be used to which this appender would register for events.
I can't speak for Ceki, but here's my 2 cents. Some applications try very hard to control the number of threads and other resources for efficiency purposes. For example, application servers are usually written in this way. In fact, the EJB specification prohibits EJB from creating their own threads. So creating hidden threads inside the logging library would not be "nice" to users working in this environment.
Ray
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
