SignalR Issue for MultipleTabs in Chrome

Question

SignalR Issue for MultipleTabs in Chrome

Jhonny Panchal 1

Hello Team,

We have implemented the SignalR service in our Angular Project. However while opening multiple tabs in chrome like 5 tabs then somehow signalR is getting disconnected in 1 or 2 tabs after 3 hours and getting the error in undefined in on close event.

However in onclose event we have the used to start the connection again, unfortunately its not connecting. Can you please help me out for the next step so I can implement for the multiple tabs

SnehaAgrawal-MSFT 22,721 Reputation points Moderator

2022-10-28T07:09:46.227+00:00

Hello @Jhonny Panchal Thanks for reaching here! Could you confirm if you are using WebSocket transport type?

Chrome has 6 concurrent http connection limit per host, but concurrent WebSocket connections per host has another larger limit (30). So as long as the SignalR connection uses WebSocket transport type, it should be able to connect more than 6 connections.

Issue 9764003: Increase number of max sockets per group for WebSocket connections. - Code Review (chromium.org)
Jhonny Panchal 1 Reputation point

2022-10-28T07:53:22.707+00:00

Hello @SnehaAgrawal-MSFT we have used the Web socket transport type.

We have also used the withAutomaticReconnect also we are refreshing the token as well for few hours token is getting refreshed and also getting reconnected Web socket. Sometimes getting error of 1006 still after that Web socket connected and getting data as well, however in 1 or 2 tabs its not getting reconnected and getting the error in onclose event undefined.
SnehaAgrawal-MSFT 22,721 Reputation points Moderator

2022-10-31T11:51:27.25+00:00

@JhonnyPanchal-23741006 can happen when WebSocket is closed by network issue. Is it that in these 1 or 2 tabs, although AutomaticReconnect is enabled, they are never able to reconnect back? What is the AutomaticReconnect logic? Having said that reached out to you internally for some more details to help you better on this.

3 answers

Your answer

SnehaAgrawal-MSFT 22,721 Reputation points Moderator

2022-10-28T07:09:46.227+00:00

Hello @Jhonny Panchal Thanks for reaching here! Could you confirm if you are using WebSocket transport type?

Chrome has 6 concurrent http connection limit per host, but concurrent WebSocket connections per host has another larger limit (30). So as long as the SignalR connection uses WebSocket transport type, it should be able to connect more than 6 connections.

Issue 9764003: Increase number of max sockets per group for WebSocket connections. - Code Review (chromium.org)
Jhonny Panchal 1 Reputation point

2022-10-28T07:53:22.707+00:00

Hello @SnehaAgrawal-MSFT we have used the Web socket transport type.

We have also used the withAutomaticReconnect also we are refreshing the token as well for few hours token is getting refreshed and also getting reconnected Web socket. Sometimes getting error of 1006 still after that Web socket connected and getting data as well, however in 1 or 2 tabs its not getting reconnected and getting the error in onclose event undefined.
SnehaAgrawal-MSFT 22,721 Reputation points Moderator

2022-10-31T11:51:27.25+00:00

@JhonnyPanchal-23741006 can happen when WebSocket is closed by network issue. Is it that in these 1 or 2 tabs, although AutomaticReconnect is enabled, they are never able to reconnect back? What is the AutomaticReconnect logic? Having said that reached out to you internally for some more details to help you better on this.

Answer 1

@SnehaAgrawal-MSFT @Bruce (SqlWork.com)

Can you please let me know how to resolve this below error in SignalR for multiple Tabs.

OnStart Error detail : Error: Unable to connect to the server with any of the available transports.
Error: WebSockets failed: Error: WebSocket failed to connect. The connection could not be found on the server,
either the endpoint may not be a SignalR endpoint, the connection ID is not present on the server, or there is a proxy blocking WebSockets.
If you have multiple servers check that sticky sessions are enabled. ServerSentEvents failed: Error: 'ServerSentEvents' is disabled by the client.
LongPolling failed: Error: 'LongPolling' is disabled by the client.

Answer 2

Jhonny Panchal 1

Thanks @Bruce (SqlWork.com) .

Can you help me out if there is any solution for this so SignalR so not disconnect if i have open multiple tabs in Chrome.

Bruce (SqlWork.com) 83,421 Reputation points Volunteer Moderator

2022-10-29T19:01:43.11+00:00

a better approach would be a common service worker that handled the signal/r connection and used messages to the other tabs

Answer 3

Bruce (SqlWork.com) 83,421 Volunteer Moderator

Chrome aggressively shuts down inactive tabs by batching timers. You must assume any logic based in timers may not run when you expect.

Share via

SignalR Issue for MultipleTabs in Chrome

3 answers

Your answer