We are imbedding Qlik visualizations in our company website and we are trying to solve an issue with WebSockets. Initially, we were opening several Qlik Applications to build the page and, in IE especially, we hit the limitation on the number of available WebSockets. We have reduced the number of WebSockets needed, but if the user opens the site on multiple tabs, we can still run out of available WebSockets.
We are trying to do one of two thing to help this. Either, determine the number of available WebSockets before we attempt to open a new Qlik Application and, if none are available, inform the user so they can close some of the open tabs. If we can't proactively determine if there is a WebSocket available, then the alternative would be to trap an error that tells us that there wasn't an available WebSocket and inform the user of the failure. Right now, all we get is a blank page with no visualizations loaded and no indication of why.
With WebSocket connections being so critical for Qlik, I am wondering if anyone else has dealt with this issue and developed a way to determine WebSocket availability, either before or after the event.
Del-
