Re: parallel deployment and websockets

2017-05-31 Thread Johan Compagner
On 31 May 2017 at 10:11, Mark Thomas wrote: > > >> > >> > > would a feature request be accepted for this that there can be a cookie > set > > where that "load balancer" would also look at? > > and that cookie always make sure that it goes to the context it started > > from as long as that contex

Re: parallel deployment and websockets

2017-05-31 Thread Mark Thomas
On 31/05/17 08:38, Johan Compagner wrote: >> >> >> It depends. If the URL in the HTTP UPGRADE request includes the session >> ID, and that session ID is still valid in ##1, then the WebSocket >> request will be handled by ##1. >> >> Mark >> >> > would a feature request be accepted for this that the

Re: parallel deployment and websockets

2017-05-31 Thread Johan Compagner
> > > It depends. If the URL in the HTTP UPGRADE request includes the session > ID, and that session ID is still valid in ##1, then the WebSocket > request will be handled by ##1. > > Mark > > would a feature request be accepted for this that there can be a cookie set where that "load balancer" wou

Re: parallel deployment and websockets

2017-05-30 Thread Ludovic Pénet
In a similar situation, I do the following : * go full stateless, use no session ; * configure WS client to frequently reconnect * use atmosphere with an internal JMS backend, such as ActiveMQ, to share data transparently between parallely deployed versions. With Atmosphere, you avoid losing mess

Re: parallel deployment and websockets

2017-05-30 Thread Johan Compagner
> > > But now i have websockets, if i connect to ##1 first and i have the end > > point there > > Then i add a ##2 version of the context > > then i guess a new user that opens a websocket will go to ##2 > > but if the existing user does a refresh in the browser then it will also > > suddenly go to

Re: parallel deployment and websockets

2017-05-30 Thread Mark Thomas
On 30/05/17 11:09, Johan Compagner wrote: > Hi, > > if i read this: > > http://tomcat.apache.org/tomcat-8.5-doc/config/context.html#Parallel_deployment > > then i see it will go to the "old" version of a war based on session > information > i guess this is jsessionid? > > So a refresh in the br

parallel deployment and websockets

2017-05-30 Thread Johan Compagner
Hi, if i read this: http://tomcat.apache.org/tomcat-8.5-doc/config/context.html#Parallel_deployment then i see it will go to the "old" version of a war based on session information i guess this is jsessionid? So a refresh in the browser or another request with the jsessionid will go to the vers