Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix for default HttpClient callback thread pool is always one.
Changing the default corePoolSize to the number of available processors. The default thead pool for running the http client async callbacks is initialized with a coreSize of 0 and a unbounded queue. The ThreadPoolExecutor creates threads just if all the coreSize threads are busy and the queue is full. Given that the default queue is unbounded, new threads are never created, hence the default-pool will never ever have more than 1 thread to execute all the callbacks. From the ThreadPoolExecutor doc (http://docs.oracle.com/javase/7/docs/api/java/util/concurrent/ThreadPoolExecutor.html): "Using an unbounded queue (for example a LinkedBlockingQueue without a predefined capacity) will cause new tasks to wait in the queue when all corePoolSize threads are busy. Thus, no more than corePoolSize threads will ever be created"
- Loading branch information