John Sourcer
Reputation: 198
IIS maximum worker processors and Signalr
I have been having a lot of trouble to get Signalr to function reliably with messages inexplicably never arriving but being sent from the Hub almost as if the groups are being lost although the websocket connection is open on two clients which I am trying to communicate between.
I noticed now that I have IIS 8.5 set at 10 maximum worker processes for the site and they are all running.
Is this possibly a cause for the erratic behavior? Should I implement a backplane even if I have just one server but multiple processes?
Any help will be much appreciated. It's been weeks. :(
Upvotes: 1
Views: 356
Answers (0)
Related Questions
- While using signalr, will there be any connection limits on IIS
- IIS 8 ASP.NET 4 Default maxWorkerThreads
- Maximum concurrent requests in signalr self hosted in kestrel
- SignalR IIS worker process does not released
- SignalR lost messages if IIS configure with more than 1 worker process
- Does running under local IIS limit the number of Signalr connections
- Maximum Worker Processors and Sessions
- SignalR: worker process is limited to 10 concurrent requests
- IIS Background thread and SignalR
- SignalR Performance with IIS 7.5