Netty 3: Blocked I/O worker threads; Netty creating new threads for every request

[swasti7]

I am creating a Netty client (AsyncHttpClient) with a fixed worker pool of 3 threads.

This enables my application to run 3 HTTP requests. However, all HTTP requests made after that are dropped as Netty does not use the existing worker threads even though it is supposed to be able to run multiple channels on the same worker thread.

I also tried sending rest of the endpoints after 30 seconds but Netty refused to reuse existing threads or create new threads to handle subsequent request. I am using Netty 3.

Shouldn't Netty use same worker thread for multiple channels (i.e multiple HTTP requests). Note I am using single client for all HTTP requests. What is the advantage of using Netty if I/O thread remains blocked and it requires to create new worker thread for handling every request. With 3 worker threads, should i not expect more than 3 HTTP requests asynchronously running ?