> is it possible for you to create simple comet application and probably
> client, which will reproduce the issue?
Sure, I will try that tomorrow.
-Jussi
On Aug 13, 2009, at 15:24 , Jussi Kuosa wrote:
> client has a timeout that kills the CONNECT HTTP connection during the
> expiration wait period. The client sends a FIN and gets an ACK from
> the
> server, so the c->s side is closed. For some reason, the server does
> not
> notice that the client has begun to close the connection and the end
> result
> is that on the client the connection waits in FIN_WAIT_2 state and the
> server has a CLOSE_WAIT connection.
--
View this message in context: http://www.nabble.com/Comet-context-doesn%27t-expire-tp24072882p24957304.html
Sent from the Grizzly - Users mailing list archive at Nabble.com.