tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nir A <...@netomedia.com>
Subject Re: Websockets with tomcat clustering and session replication
Date Tue, 03 Dec 2013 07:54:11 GMT
Yeah but, I would like to link the websocket session with the http session
of the handshake. and that way i will be able to imitiate the session
replication abilities for websocket.

This mechanism works as intended only problem is the replication not
replicate http session attribute while the websocket connection is
happening (since this is not a regular httpsession \ request cycle) my
question is - can i activate manually some kind of action on the http
session to make it "Refresh" so the tomcat will replicate it every time i
set new attribute? (I remind you again that pressing f5 will reconnect the
websocket and the attributes are being copied).


Thanks.


On Dec 2, 2013 8:51 PM, "Rossen Stoyanchev" <rstoyanchev@gopivotal.com>
wrote:

> On Sun, Dec 1, 2013 at 4:33 PM, Nir A <nir@netomedia.com> wrote:
>
> My POC web application has one html page with javascript web socket
> > send\recieve messages.
> >
> > What i did notice that might shade light on whats the problem is the
> > following scenario:
> >
> > If i press f5 on the browser, the web page is loaded and a new http
> > handshake is taking place. when that happens all the attributes do
> > replicate!!!
> >
> > Is there a way to make the attribute replicate without the need of
> > refreshing the page?
> >
>
> In HTTP you have many requests associated with a session id. With session
> replication, each new request could go to a different server and still
> access the same HTTP session attributes.
>
> In WebSocket on the other hand there is a single connection the server and
> if you lose it, you have to reconnect, which is probably what pressing F5
> does for you. Unless I'm missing something, you have to detect when the
> WebSocket connection is closed on client side and reconnect.
>
> Rossen
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message