Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Waiting for Available Sockets in ASP.NET using SignalR

I am using SignalR to implement the Chat in asp.net but when I open multiple tabs of my web application I am getting "Waiting for Available Sockets...".

I have implemented all settings specified on Performance Tuning SignalR but my problem is not getting solved from this.

How can I resolve this issue?

like image 511
G.S Bhangal Avatar asked Sep 04 '14 14:09

G.S Bhangal


People also ask

How long do SignalR connections stay open?

The default keepalive timeout period is currently 20 seconds. If your client code tries to call a Hub method while SignalR is in reconnecting mode, SignalR will try to send the command.

Does SignalR use WebSockets?

ASP.NET Core SignalR is a library that simplifies adding real-time web functionality to apps. It uses WebSockets whenever possible. For most applications, we recommend SignalR rather than raw WebSockets.

What does waiting for available socket mean in Chrome?

You can get the “Waiting for available sockets” error in Chrome when the connection sockets get overloaded. Freeing up the sockets can resolve this issue for good. Flushing the sockets will make them available for your connection. Type “Chrome://net-internal” (no quotes) into the address bar and hit the Enter key.


1 Answers

As already indicated in the comments, you're hitting the connection limit per hostname which is enforced by the browser.

Your basic options are

  • single page app that has tabs in its UI so the user doesn't have to use browser tabs
  • sharing the connection in some way, e.g. as discussed in this question
  • separate subdomains
like image 73
Lars Höppner Avatar answered Oct 11 '22 12:10

Lars Höppner