Thread Pooling (was Efficient CPU usage with recursively parallelizable problem)

chucky wrote:


No, I don't think it does. Imagine a sub-class of of Thread that
does
something like this:

class PoolThread extends Thread {

  volatile Runnable task;
  volatile boolean done = true;

  synchronized public void start() {
    for( ;; ) {
      while( task == null ) {
        wait();
      }
      done = false;
      try {
        task.run();
      }
      finally {
        done = true;
      }
    }
  }
}

Now you have a Thread class that can be re-used. If "done" is true,
you can see if the thread is still running (if it is, no errors were
thrown). If the thread is running and the done flag is set, then we
can reuse the task, set it to a different task, and notifyAll() on
the
thread to wake it up and cause it to execute the next task.

If the task throws an exception, then the thread will stop, but I
think that's required. Normally after your thread does throw an
exception, it's replaced, not reused.