SignalR：工作进程限制为10个并发请求

本文介绍了SignalR：工作进程限制为10个并发请求的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我已将基于SignalR的应用程序部署到我的本地服务器上，当有超过10个并发用户时，它会崩溃。

I've deployed a SignalR-based app onto my on-premises server, and it is crashing when there are more than ten concurrent users.

与我的应用程序池关联的工作进程的长时间运行请求都具有 / signalr / reconnect？transport = serverSentEvents& connectionToken = ... 。

The long-running requests for the worker process associated with my app pool all have URLs of the form /signalr/reconnect?transport=serverSentEvents&connectionToken=....

一旦超过十个用户连接，就会破坏十个并发请求的限制并且应用程序挂起。

As soon as more than ten users connect, the limit of ten concurrent requests is breached and the application hangs.

我是否需要更改任何IIS设置以允许SignalR在此实例中扩展？如果我正在部署到Azure，我将如何配置设置以考虑到这一点？

Do I need to change any IIS settings to allow SignalR to scale in this instance? If I'm deploying to Azure, how would I configure the settings to take account of this?

推荐答案

工作站操作系统（Windows XP） ，Vista，7,8等）有最多10个并发连接的限制。这些操作系统不打算用作服务器（我认为EULA禁止它，我记得）。并发连接限制是Microsoft强制执行非服务器限制的一种方式。

Workstation OSes (Windows XP, Vista, 7, 8, etc) have a limit of at most 10 concurrent connections in IIS. These OSes are not intended for use as a server (and I think the EULA prohibits it, as I recall). The concurrent connection limit is one way that Microsoft enforces the "not a server" restriction.

Windows Server操作系统（Server 2008 R2，Server 2012等）没有这个限制限制，因此在将应用程序部署到生产服务器时不会出现此问题。 Windows Azure也很好（它是幕后的Windows Server）。

Windows Server OSes (Server 2008 R2, Server 2012, etc) do not have this restriction, and so you won't have this problem when you deploy you application to a production server. Windows Azure is fine also (it is Windows Server behind the scenes).