问题描述
我们在IIS安装的应用程序事件查看器中收到了一些警告。我们有一个包含两个网站（ColdFusion网站，而不是.NET）的AppPool设置。
事件查看器显示以下警告：
在关闭期间，服务应用程序池HighPriorityApps的进程超过时间限制
。进程标识为175540。
任何想法要做什么来整理这一个或从哪里开始寻找解决方案？
我们修复了一个类似的单独配置问题。
这里的帮助是Microsoft IIS 6.0管理员的口袋调查员William R Stanek。
我会在这里帮助。
在我的公司，我们总是将单独的站点拆分为单独的应用程序池，并在其上运行ColdFusion。
对于每个池，我们设置了以下设置。
右键单击应用程序池中的池
回收工作进程1740，一切都清楚
我们还确保工作进程的最大数目为4。
空闲20分钟后将工作进程限制为内核请求队列为1000
我们每30秒ping一次工作进程
$ b $
您还应该检查您的IIS中的应用程序配置是否在网站上属性框/主目录/配置，您将.cfm的扩展名设置为JRUN / CF dll以及通配符应用程序映射。
我们删除了通配符应用程序地图，因为我们发现jrun在图像上被轮询，所有排序只是说，它不会处理他们。
在网站属性中检查ISAPI过滤器，如果你不使用.NET，然后确保它不是作为过滤器运行在这里，因为它可能只是
您在ColdFusion中检查了平均队列长度和队列时间。尝试Fusion Reactor在这里找到问题。可能是你的网站太忙了，我怀疑这一点，因为CF将在IIS之前爆发。
We're getting a number of warnings in the Application Event Viewer on our IIS installation. We have an AppPool set up which contains two websites (both ColdFusion sites, not .NET).
The Event Viewer shows the following warning:
A process serving application pool 'HighPriorityApps' exceeded time limits
during shut down. The process id was '175540'.
Any ideas what to do to sort this one out or where to begin looking for solutions?
We fixed a similar problem with config alone.
A great book to help here is Microsoft IIS 6.0 Administrator's Pocket Cunsultant by William R Stanek.
I'll try to help here. I've seen this before.
At my company we always split the separate sites into separate Application pools with ColdFusion running on them
For each Pool we have the following settings set up.
Right click on your Pools in Application poolsRecycle worker process (in minutes) 1740, everything else clear
We also make sure that Maximum number of worker processes is 4.
We shutdown worker processes after being idle for 20 mins, limit the kernel request queue to 1000
We ping the worker process every 30 seconds
That serves many tens of Millions of page views across 4 servers per month.
You should also check whether in your IIS "Application configuration" in the web site properties box/Home Directory/Configuration you have both the Extensions for .cfm set to the JRUN/CF dll as well as the wildcard application map.
We removed the wildcard application map as we found that jrun was getting polled on images and all sorts only to say it wouldn't process them.
Also in Web Site properties check the ISAPI Filters, if you don't use .NET then make sure it is not running as a filter in here as it could be just the filter that's causing the thing to blow up.
Have you checked the average queue length and queue time in ColdFusion. Try out Fusion Reactor to find problems here. It could be that your web site is just too busy, I doubt this though as CF would be blowing up before IIS.
这篇关于IIS AppPool错误（1013 - W3SVC）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！