同时启动应用程序池会导致与最大并发外壳数有关的错误 [英] Starting application pool concurrently causes error related to maximum number of concurrent shells
问题描述
我有一个Powershell脚本，可以异步运行以启动多个应用程序池。
I have a powershell script which can run asynchorusly to start multiple application pools.
但是当我有一定数量的应用程序池要启动时，会引发以下错误：
But when i have a certain amount of app pools to start it throws the following error:
由于首选项变量
ErrorActionPreference或公共参数设置为Stop，因此正在运行的命令停止了：[ServerX]
连接到远程服务器XXX失败，并显示以下错误
消息：WS-Management服务无法处理该请求。该
用户已超出此插件
允许的并发shell的最大数量。关闭至少一个打开的外壳，或为此用户提高插件配额
。有关更多信息，请参见
about_Remote_Troubleshooting帮助主题。
The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: [ServerX] Connecting to remote server XXX failed with the following error message : The WS-Management service cannot process the request. This user has exceeded the maximum number of concurrent shells allowed for this plugin. Close at least one open shell or raise the plugin quota for this user. For more information, see the about_Remote_Troubleshooting Help topic.
每个用户的最大外壳数为10000。
The maximum shells per user is 10000.
appcmd运行时似乎有很多其他事情发生，但不确定如何解决此问题
It seems that there is more happening beneath the hood when appcmd runs but not sure how i can get around this issue
任何建议会很棒
下面是winrs配置
Type Name SourceOfValue Value
---- ---- ------------- -----
System.String AllowRemoteShellAccess true
System.String IdleTimeout 7200000
System.String MaxConcurrentUsers 10
System.String MaxShellRunTime 2147483647
System.String MaxProcessesPerShell 25
System.String MaxMemoryPerShellMB 1024
System.String MaxShellsPerUser 10000
推荐答案
cd WSMan:\localhost\Shell
Set-Item .\MaxProcessesPerShell 10000
这篇关于同时启动应用程序池会导致与最大并发外壳数有关的错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
