CLOSE WAITS ON NETTY SERVER

[Mark_K]

The problem with using netty threads to do business logic, no matter how many
you have is that you are artificially limiting the number of requests netty
can handle.  You would not be utilizing the power of your hardware by
setting a limit on the number of concurrent requests your server can handle.
Netty spawns 1 thread per core on the machine by default. This is sufficient
for handling vast numbers of requests, as long as you don't tie up the
threads.  We maintain persistent connections to our server from devices out
on the web and use our own queueing and execution thread pool to handle the
requests asynchronously. Netty threads pass requests into our queue which
gets processed by our worker threads.

Mark.

-- 
View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/CLOSE-WAITS-ON-NETTY-SERVER-tp5961429p5966518.html
Sent from the Netty User Group mailing list archive at Nabble.com.