> 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. I agree. However, the use of java.util.Timer will not resolve that (since it has a thread inner class itself). I think that in such cases, enterprise server specific appenders are in order... no?
You have a good point. The fact that java.util.Timer is part of the JDK might make a difference but probably not.
-- Ceki Gülcü
For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
