Re: websocket endpoints not released

2018-09-05 Thread Johan Compagner
ne (at least with my > application running on Tomcat) > > -Original Message- > From: Johan Compagner [mailto:jcompag...@servoy.com] > Sent: Wednesday, September 05, 2018 3:42 AM > To: Tomcat Users List > Subject: Re: websocket endpoints not released > > - - - exter

RE: websocket endpoints not released

2018-09-05 Thread Louis Zipes
AM To: Tomcat Users List Subject: Re: websocket endpoints not released - - - external message, proceed with caution - - - If a user refreshes the browser then the current ws is always closed and a new one is opened Op za 1 sep. 2018 02:38 schreef Alex O'Ree : > I ran into a stran

Re: websocket endpoints not released

2018-09-05 Thread Johan Compagner
If a user refreshes the browser then the current ws is always closed and a new one is opened Op za 1 sep. 2018 02:38 schreef Alex O'Ree : > I ran into a strange issue today. Running tomcat 8.5 with a websocket > endpoint + some javascript to wire up a browser to the socket. All works as > nor

websocket endpoints not released

2018-08-31 Thread Alex O'Ree
I ran into a strange issue today. Running tomcat 8.5 with a websocket endpoint + some javascript to wire up a browser to the socket. All works as normal, however sometimes if the user refreshes the browser, it seems as if second web socket is opened by the browser. This leads to the user seeing dup