Impossible to make a cached thread pool with a size limit?

by

The ThreadPoolExecutor has the following several key behaviors, and your problems can be explained by these behaviors.

When tasks are submitted,

  1. If the thread pool has not reached the core size, it creates new threads.
  2. If the core size has been reached and there is no idle threads, it queues tasks.
  3. If the core size has been reached, there is no idle threads, and the queue becomes full, it creates new threads (until it reaches the max size).
  4. If the max size has been reached, there is no idle threads, and the queue becomes full, the rejection policy kicks in.

In the first example, note that the SynchronousQueue has essentially size of 0. Therefore, the moment you reach the max size (3), the rejection policy kicks in (#4).

In the second example, the queue of choice is a LinkedBlockingQueue which has an unlimited size. Therefore, you get stuck with behavior #2.

You cannot really tinker much with the cached type or the fixed type, as their behavior is almost completely determined.

If you want to have a bounded and dynamic thread pool, you need to use a positive core size and max size combined with a queue of a finite size. For example,

new ThreadPoolExecutor(10, // core size
    50, // max size
    10*60, // idle timeout
    TimeUnit.SECONDS,
    new ArrayBlockingQueue<Runnable>(20)); // queue with a size

Addendum: this is a fairly old answer, and it appears that JDK changed its behavior when it comes to core size of 0. Since JDK 1.6, if the core size is 0 and the pool does not have any threads, the ThreadPoolExecutor will add a thread to execute that task. Therefore, the core size of 0 is an exception to the rule above. Thanks Steve for bringing that to my attention.

More Related Contents:

  1. Executors.newCachedThreadPool() versus Executors.newFixedThreadPool()
  2. How to wait for all threads to finish, using ExecutorService?
  3. ExecutorService that interrupts tasks after a timeout
  4. Handling exceptions from Java ExecutorService tasks
  5. How to properly use Java Executor?
  6. What are the advantages of using an ExecutorService?
  7. Java’s Fork/Join vs ExecutorService – when to use which?
  8. ThreadPoolExecutor Block When Queue Is Full?
  9. Java ExecutorService: awaitTermination of all recursively created tasks
  10. ThreadPoolExecutor Block When its Queue Is Full?
  11. How to pause/resume all threads in an ExecutorService in Java?
  12. Handling Exceptions for ThreadPoolExecutor
  13. Dynamic Thread Pool
  14. ExecutorCompletionService? Why do need one if we have invokeAll?
  15. What’s the difference between Thread start() and Runnable run()
  16. What’s a monitor in Java?
  17. Turning an ExecutorService to daemon in Java
  18. Is ExecutorService (specifically ThreadPoolExecutor) thread safe?
  19. Java threads and number of cores
  20. When should I use a CompletionService over an ExecutorService?
  21. Forcing multiple threads to use multiple CPUs when they are available
  22. How to use invokeAll() to let all thread pool do their task?
  23. Why does Java not see the updated value from another thread?
  24. What is adaptive spinning w.r.t lock acquisition?
  25. How to shutdown an ExecutorService?
  26. Thread Confinement
  27. How can I wrap a method so that I can kill its execution if it exceeds a specified timeout?
  28. ExecutorService vs Casual Thread Spawner
  29. Java, divide incoming work uniformly via hashing in multithreaded evnironments
  30. Controlling Task execution order with ExecutorService

Leave a Comment