users@grizzly.java.net

Re: Comet Streaming Timeout

From: Jeanfrancois Arcand <Jeanfrancois.Arcand_at_Sun.COM>
Date: Fri, 10 Jul 2009 11:30:19 -0400

Salut,

Pred wrote:
> Hi,
>
> whenever the browser is not closed normally (for example the network cable
> has been unplugged or the device disabled) the underlying TCP Connection on
> the server stays alive:
>
> netstat -tapn Output:
>
> Proto Recv-Q Send-Q Local Address Foreign Address State
> PID/Program name
> tcp6 0 437 192.168.1.48:8080 192.168.1.66:2332
> CONNECTED 3961/java
>
> Handlers still send data and the Send-Queue fills.
> After about ~19 minutes the TCP Connection is recognized as being dead and
> "onInterrupt" is called.
>
> Where can I configure this "timeout" value? Im using glassfish v3 B47.4
> I have already tried "write-timeout-millis" but it does not work.
>
> I have the same issue in Tomcat (using CometProcessor not Grizzly).

That's strange as by default Grizzly Comet detect disconnection for
client via a CometEvent.INTERRUPT event. Do you have a test case I can
play with?

BTW I see you are using two Comet implementation. I recommend you take a
look at:

    * http://atmosphere.dev.java.net

It's my new project based on what learned with grizzly comet...working
on all web server.

Thanks

-- Jeanfrancois


>
> Thanks for help!
>
> Bye
> Markus