logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bauman, Nick" <nick_bau...@retek.com>
Subject RE: Daemon Thread for AsyncAppender
Date Thu, 26 Sep 2002 14:30:45 GMT
This makes it configurable, ie, the consumer decides whether log4j's threads
will be reaped when they exit or not. There are good reasons for either
behavior. IMHO, you don't want the Dispatcher to assume daemon or not, you
want it configurable. Am I overstating the case, or is it clear?

-----Original Message----- 
From: Ceki Gülcü [mailto:ceki@qos.ch] 
Sent: Thu 9/26/2002 9:16 AM 
To: Log4J Developers List 
Cc: 
Subject: RE: Daemon Thread for AsyncAppender




I don't understand. The Dispatcher thread is already marked as a daemon (as
of log4j 1.2.4). What gives?

At 09:08 26.09.2002 -0500, you wrote:
>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: mwomack@apache.org [mailto:mwomack@apache.org
<mailto:mwomack@apache.org> ]
>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> 
><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:nick_bauman@retek.com
<mailto:nick_bauman@retek.com> 
><mailto:nick_bauman@retek.com <mailto:nick_bauman@retek.com> > ]
> > Sent: Friday, September 20, 2002 8:07 AM
> > To: log4j-dev@jakarta.apache.org
> > 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:log4j-dev-unsubscribe@jakarta.apache.org
><mailto:log4j-dev-unsubscribe@jakarta.apache.org
<mailto:log4j-dev-unsubscribe@jakarta.apache.org> > >
> > For additional commands, e-mail:
> > <mailto:log4j-dev-help@jakarta.apache.org
><mailto:log4j-dev-help@jakarta.apache.org
<mailto:log4j-dev-help@jakarta.apache.org> > >
> >
>
>
>
>
>--
>To unsubscribe, e-mail:   <mailto:log4j-dev-unsubscribe@jakarta.apache.org
<mailto:log4j-dev-unsubscribe@jakarta.apache.org> >
>For additional commands, e-mail: <mailto:log4j-dev-help@jakarta.apache.org
<mailto:log4j-dev-help@jakarta.apache.org> >

--
Ceki

TCP implementations will follow a general principle of robustness: be
conservative in what you do, be liberal in what you accept from
others. -- Jon Postel, RFC 793



--
To unsubscribe, e-mail:   <mailto:log4j-dev-unsubscribe@jakarta.apache.org
<mailto:log4j-dev-unsubscribe@jakarta.apache.org> >
For additional commands, e-mail: <mailto:log4j-dev-help@jakarta.apache.org
<mailto:log4j-dev-help@jakarta.apache.org> >




Mime
View raw message