CODEWITHSUNDEEP
netty
user3757955
user3757955

Reputation: 88

Is it possible to use a separate thread pool for opening connections in Netty?

When using Netty for a client application and sharing your I/O thread pool between connections, it is possible for connects/reconnects to exhaust the I/O thread pool if the number of connections exceed the size of the thread pool. This can potentially block existing connections from reading until the connect timeout arrives.

Does the Netty API expose a way to specify a separate thread pool that is only used for opening connections? Or is there a better way to address this problem?

Upvotes: 0

Views: 259

Answers (1)

Norman Maurer
Norman Maurer

Reputation: 23557

No there is no way to use a separate thread pool here. That said there is no "blocking" even in the case of connection timeouts as everything is handled in an async fashion

Upvotes: 2

Related Questions