Question

I just want to insert a batch of tasks into it, and do not want to lost any one.

Answer 1

@virsir,

You’d asked specifically about creating an instance ThreadPoolExecutor. But I’m wondering whether it would be okay to have any class that implements the ExecutorService interface. Since ThreadPoolExecutor implements ExecutorService, this isn’t much of a leap.

The java.util.concurrent.Executors class provides some useful functions for creating thread pools that handle some common situations.

I’ve recently used Executors.newFixedThreadPool() in a project to create several different thread pools. It returns an object that implements ExecutorService. I had no trouble submitting tens of thousands of Runnable instances to a pool of 10 threads, and it worked quite smoothly.

Per the Java 5 docs, this method:

Creates a thread pool that reuses a
fixed set of threads operating off a
shared unbounded queue. If any thread
terminates due to a failure during
execution prior to shutdown, a new one
will take its place if needed to
execute subsequent tasks.

Since the method is said to create an “unbounded queue”, there should be no artificial limits on the number of tasks one can submit.