[concurrency-interest] Serialized ThreadPoolExecutor

Norman Elton normelton at gmail.com
Mon Jul 20 13:31:39 EDT 2009

Erkin & Jim,

Thanks for your replies. It seems that both your suggestions have a
common downside... If I do the locking inside the job, then a
"waiting" job will occupy one of the threads in my pool. If ten jobs
come in with the same "key", each of which takes one second to
execute, that could impact unrelated jobs. I'd rather other jobs
continue to be scheduled and executed.


Thanks again,


More information about the Concurrency-interest mailing list