Jeremy, Apologies if you have received my earlier email (my internet mail account doesn't seem to work always)
Executors.newFoxedThreadPool() creates a thread pool backed by an unbounded queue. This means even when all threads are in use, work won't be rejected. In terms of when and where the workAccepted method is invoked, can we say is an implementation detail, as long as the order in which the callbacks are executed are guaranteed. Alternatively, we could wait on workAccepted callback on the monitor for the work item before calling workStarted. Ta Meeraj -----Original Message----- From: Jeremy Boynes [mailto:[EMAIL PROTECTED] Sent: 24 July 2006 19:05 To: [email protected] Subject: Re: [jira] Created: (TUSCANY-573) Race condition in ThreadPoolWorkManager On Jul 24, 2006, at 10:34 AM, Jeremy Boynes wrote: > Does this still fulfill the lifecycle contract? With this patch, > workAccepted is called on the worker thread and not until the work is > actually dispatched - I thought it would need to be called before any > scheduling delay. > The patch does seem to fix the problem but I'm not sure about committing it due to the above question ... -- Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message has been checked for all email viruses by MessageLabs. ***************************************************** You can find us at www.voca.com ***************************************************** This communication is confidential and intended for the exclusive use of the addressee only. You should not disclose its contents to any other person. If you are not the intended recipient please notify the sender named above immediately. Registered in England, No 1023742, Registered Office: Voca Limited Drake House, Three Rivers Court, Homestead Road, Rickmansworth, Hertfordshire, WD3 1FX This message has been checked for all email viruses by MessageLabs. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
