Same behavior with Internet Explorer? I know that in general, Chrome tabs act as the same session if you open more than one (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 - - - 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 <alexo...@apache.org>: > 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 > duplicate messages which can be confusing. I do have code on the page for > navigation links to close the socket but i'm thinking i haven't handled all > cases. My assumption was that a full browser reload would trigger any open > websockets to close, but apparently they don't (at least with chrome). Has > anyone else ran into a similar issue? > --------------------------------------- CONFIDENTIALITY NOTICE: This message is for intended addressee(s) only and may contain information that is confidential, proprietary or exempt from disclosure. If you are not the intended recipient, please contact the sender immediately. Unauthorized use or distribution is prohibited and may be unlawful. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
