
Signature
Christopher Benson-Manica | I *should* know what I'm talking about - if I
ataru(at)cyberspace.org | don't, I need to know. Flames welcome.
> The Sun documentation says that shutdownNow() is only a "best-effort"
> attempt to end all processing tasks. Is it reasonable to assume that
[quoted text clipped - 4 lines]
> that in all likelihood coding for Thread.interrupt() will be
> sufficient, but I find the Sun documentation to be uncomforting.
The JavaDocs say that "typical implementations" will cancel via
Thread.interrupt(). This indicates that it is not required by the contract
of this method that Thread.interrupt() actually be the mechanism used for
cancelling tasks.
In other words, I'd probably avoid using this shutdownNow() method if I
were you.
Perhaps if you were using a specific implementation (e.g.
ThreadPoolExecutor), you could find a firmer, publicly documented contract.
- Oliver
Christopher Benson-Manica - 15 Jun 2006 13:40 GMT
> Perhaps if you were using a specific implementation (e.g.
> ThreadPoolExecutor), you could find a firmer, publicly documented contract.
I will take a look at using a ThreadPoolExecutor for this task. Thank
you for your helpful reply.

Signature
Christopher Benson-Manica | I *should* know what I'm talking about - if I
ataru(at)cyberspace.org | don't, I need to know. Flames welcome.