Re: [jetty-users] WebSocket auto disconnect after 30sec ?

[go canal <gocanal@xxxxxxxxx>]

I realize that WebSocket uses the same setting for HTTP connection, so we can change this maxIdleTime (in ms)
 

rgds,
canal

---

From: Erin Drummond <erin.dru@xxxxxxxxx>
To: JETTY user mailing list <jetty-users@xxxxxxxxxxx>
Sent: Mon, January 18, 2010 4:35:10 PM
Subject: Re: [jetty-users] WebSocket auto disconnect after 30sec ?

I have noticed the same thing using a Java WebSocket client, so it
looks like the server sees the socket is inactive and closes it after
30 seconds of inactivity (this makes sense I think if the users
browser crashes or they close the tab etc)

I was going to get around it by sending Ping? Pong! messages (similar
to you), but I wonder if there is a better way.

On Mon, Jan 18, 2010 at 7:10 PM, go canal <gocanal@xxxxxxxxx> wrote:
> I am not sure this is a browser issue, I am using Chrom. WebSocket is
> automatically disconnected after 30 sec.
> it is
> mentioned http://www.therichwebexperience.com/blog/greg_wilkins/2009/11/jetty_websocket_server
> what's the best practice of keeping the connection ? keep sending 1-byte
> dummy data ? that's sounds unacceptable....
>
> rgds,
> canal
>
>
> _______________________________________________
> jetty-users mailing list
> jetty-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-users
>
>
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-users