On Tuesday 28 May 2002 09:51 pm, Gregory Steuck wrote: > >>>>> "Peter" == Peter Royal <[EMAIL PROTECTED]> writes: > > Peter> On Tuesday 28 May 2002 07:34 pm, Gregory Steuck wrote: > >> toast. Thus, we should not continue banging on it and the only > >> thing TPCThreadManager.run can do is exit (possibly logging the > >> exception, this is not in the patch below). > > Peter> I think that should be the responsibility of the object > Peter> that is managing the TPCThreadManager. > > If understand you correctly, you suggest that the caller of > TPCThreadManager.run should log the exception? This may not be really > feasible: run() is called by that same thread pool that just aborted, > so it is presumably badly broken. Thoughts?
(note to self, don't think hard about programming after beer + mexican food) May we just have to log a FATAL_ERROR and hope for the best? I haven't done a ton of thread-intentive programming, and thus I'm unsure of other possible alternatives. -pete -- peter royal -> [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
