We have some problems with the server and we are trying to eliminate all possible problems. I checked the Workflow view in the IIS management tool and opened the view by opening the worker process with errors and saw one of the elements of the signalR connection record:
http://srv03.green-parrot.net/api2/Test.png
We use signalR for only one page. The user starts a new search, and we push the results with a signal to the user. Then we keep the connection open for another search. I found a similar question here: https://github.com/SignalR/SignalR/issues/3295 , but they are not talking about EndRequest. I also checked the connection timeout, and it is configured for 20,000 ms, so after this time the client should automatically connect (or no longer respond).
Question: Is this normal, and if not, what can I do?
Btw: we are working on a R 2.2 signal, and the client IP is a loadbalancer. I asked the same question: https://github.com/SignalR/SignalR/issues/3431 , but I found out that there are almost no answers in recent days.
source
share