FULL PRODUCT VERSION :


A DESCRIPTION OF THE PROBLEM :
If you read the paragraph titled "Core and maximum pool sizes", it doesn't state what happens if the number of running threads is *equal to* corePoolSize.

"[...]
When a new task is submitted [...], and fewer than corePoolSize threads are running, a new thread is created to handle the request[...]. If there are more than corePoolSize but less than maximumPoolSize threads running, a new thread will be created only if the queue is full. [...]"

As ThreadPoolExecutor's behaviour is already confusing for many developers, this documentation should be more precise.


REPRODUCIBILITY :
This bug can be reproduced always.