Salut,
I did a test today to see if I can reproduce your issue. One thing that scared me is the fact you are experiencing CLOSE_WAIT socket. I created an OOM and see how GF was reacting. It's possible that the out of memory error is causing threads to terminate (with the uncaught exception) with the result that they aren't calling the close method (connections can stay in the CLOSE_WAIT forever until the close method is invoked). I'm not sure I can fix that in Grizzly, but I suspect that's the only way the socket can stay in the CLOSE_WAIT state. So if you fix the application OOM I suspect sockets will always get closed.
A+
-- Jeanfrancosi
[Message sent by forum member 'jfarcand' (jeanfrancois.arcand_at_sun.com)]
http://forums.java.net/jive/thread.jspa?messageID=364670