That sure as hell would fix the problem. This is what caused me to investigate the issue further. I'll prepare the patch during my lunch break today.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thu 9/26/2002 12:41 AM To: Log4J Developers List Cc: Forsyth, Zachary; Bauman, Nick Subject: RE: Daemon Thread for AsyncAppender Nick, would this also solve log4j bug#9750? http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9750 <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9750> I think we would be interested in your patch. Post it when you have a chance. -Mark > -----Original Message----- > From: Bauman, Nick [mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ] > Sent: Friday, September 20, 2002 8:07 AM > To: [EMAIL PROTECTED] > Cc: Forsyth, Zachary > Subject: Daemon Thread for AsyncAppender > > > Would the log4j developers be interested in a patch to log4j that allows a > boolean mutator on AsynchAppender's constructor to have its Dispatcher > thread to be a daemon instead of a normal one? I find this feature very > useful for running a project in a commercial application server which does > not give me a way to call close() on AsynchAppender. > > Thanks for your time > > Nick Bauman > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
