Client WebSocket disconnects when browser is minimized or not in focus - Chrome
Here's a tip for anyone using websockets and chrome to establish a connection to their PubSub+ broker.
You might be experiencing websocket disconnects after 5-6 minutes of your chrome browser being minimized or out in focus. The session disconnects with the message "Connection closed: 1001 Going Away (The endpoint is going away due to a server failure or client navigation), clean closure: true"
This conflicts with the default web-transport inactive-timeout setting that is set to 30s on client profiles.
To avoid the issue, either
2. change the web-transport inactive-timeout in the client profile to more than 60 seconds.