tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Johan Compagner <jcompag...@servoy.com>
Subject Re: Websockets with tomcat clustering and session replication
Date Mon, 02 Dec 2013 13:10:59 GMT
The problem is i guess, that you access the http session outside of a
normal http request cycle
So tomcat doesn't notice anything

And also is it not a "spec" or behavior requirement that you don't hold on
to your http session objects outside of requests?




On 1 December 2013 15:33, Nir A <nir@netomedia.com> wrote:

> Hi,
>
> Ive asked here before about how do i get a session replication over
> websockets sessions.
> Mark Thomas  answered me that i should try and link the httpsession with
> the websocket and then i will gain the replication abilities.
>
> So, I listended and implemented it just like in this url:
>
> http://stackoverflow.com/questions/17936440/accessing-httpsession-from-httpservletrequest-in-a-web-socket-socketendpoint
>
> So now, I'm able to get the session for each client. and I Do get
> replication! pretty nice!
>
> Only problem is,  While i'm adding new attributes to the primary session
> (in tomcat#1 for example) , the replicated sessions (in tomcat#2 for
> example) does NOT contain any attribues.
> The session backup is there but no attributes at all.
>
>
> 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?
>
> Thanks!
>



-- 
Johan Compagner
Servoy

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