[concurrency-interest] NullPointerException after removing alltasks from a ThreadPoolExecutor

Norman Elton normelton at gmail.com
Mon Sep 5 15:39:17 EDT 2005

Thanks for the follow-up. The "tThread" naming was actually a  
misnomer. In the implementation, it's a Runnable, not a thread.

As far as the NullPointerException, Doug Lea just responded offline  
(perhaps there's a list post coming soon) pointing to...


Thanks all,


On Sep 5, 2005, at 3:29 PM, Peter Veentjer - Anchor Men wrote:

> You shouldn't use Threads but use runnable`s. The  
> ThreadPoolExecutor has is own pool of thread (hence the name).
> I don't know the cause of the NullPointerException.

More information about the Concurrency-interest mailing list