CLOSE WAITS ON NETTY SERVER

[Mark_K]

We had a similar issue. It was due to two things:

1) We had connection cleanup code in our implementation of the
SimpleChannelUpstreamHandler. This code would end up running in the Netty
thread and consume it for much too long due to DB updates, etc.  This caused
Netty to run our of threads to process incoming requests. Solution was to
offload the logic into one of our application threads instead and release
the Netty thread ASAP. This goes for all handler methods, in fact.

2) Java JDKs have major performance issues with NIO. We upgraded to JDK
1.6.0_20 and the CLOSE_WAITS were gone. Seems that there is some locking or
contention for release of resources which gets locked up and the CLOSE_WAITS
keep growing.

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