Author gdb
Recipients asksol, gdb, jnoller
Date 2010-07-20.22:31:29
SpamBayes Score 0.0711087
Marked as misclassified No
Message-id <1279665094.33.0.588784901531.issue9205@psf.upfronthosting.co.za>
In-reply-to
Content
At first glance, looks like there are a number of sites where you don't change the blocking calls to non-blocking calls (e.g. get()).  Almost all of the get()s have the potential to be called when there is no possibility for them to terminate.

I might recommend referring to my original termination.patch... I believe I tracked down the majority of such blocking calls.

In the interest of simplicity though, I'm beginning to think that the right answer might be to just do something like termination.patch but to conditionalize crashing the pool on a pool configuration option.  That way the behavior would no worse for your use case.  Does that sound reasonable?
History
Date User Action Args
2010-07-20 22:31:34gdbsetrecipients: + gdb, jnoller, asksol
2010-07-20 22:31:34gdbsetmessageid: <1279665094.33.0.588784901531.issue9205@psf.upfronthosting.co.za>
2010-07-20 22:31:30gdblinkissue9205 messages
2010-07-20 22:31:29gdbcreate