Hi All,
We've recently encountered an issue wherein when our .Net Zero application is ruinning on a domain (but not in LocalHost) using Chrome, if you have several tabs open all to the same domain app instance, loading tabs and/or calls to the application hang, and Chrome displays a notification in the bottom left hand corner, saying "Waiting for avalible socket". When this is present, the app comes to a standstill on the client, and remains this way until tabs are closed, freeing up sockets and allowing the waiting calls to process.
We've investigated as to what was blowing out Chromes socket connection allowances, and as far as we can tell, it's SignalR's requests that are largly responsible for consuming the avalible sockets. Disabling the Chat feature (which uses SignalR) and disabling the following to SignalR scripts:
<script src="@(ApplicationPath)lib/@@aspnet/signalr/dist/browser/signalr.min.js/signalr.min.js" asp-append-version="true"></script>
<script src="@(ApplicationPath)lib/abp-web-resources/Abp/Framework/scripts/libs/abp.signalr-client.js" asp-append-version="true"></script>
Seems to have stopped the issue, and our app can be used with as many requests as we like, without encountering the socket availability issue, albeit at the cost of any functionality that uses SignalR.
Has this been encountered by anyone else, and therefore, does someone know how to resolve this without removing SignalR, or is this a new issue?
7 Answer(s)
-
0
How many tabs?
-
0
Hi Aaron,
It can be as little as two/three tabs, and more easily produced with more tabs than that.
-
0
Did you try on a different machine?
-
0
Yes - the issue has been encountered on three different client machines.
-
0
Can you reproduce it with a fresh download?
-
0
We don't have the time or resources to set up another server instance to test for the issue in a fresh download, but what we could do it create an account on one of our environments for you, so that you're able to investigate?
-
0
we could do it create an account on one of our environments for you, so that you're able to investigate?
@davidharrison
It would be great, please send credentials to [email protected].
