blocks|key|3326981|text|在IIS6中，转到应用程序池部分，然后在托管有问题的ASP.NET应用程序的池上右击>属性。转到Performance选项卡，取消选中“在空闲时间后关闭工作进程：”|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3326982|在IIS7中，转到连接窗格并找到应用程序池，然后为托管应用程序的池选择高级设置。找到"Idle+Timeout“属性并将其设置为"0”(这将禁用它)。|3326983|默认值为20分钟不活动。通过取消选中该框，一旦worker+process加载了您的AppDomain，它将永远不会死(当然，除非您终止该进程或其他什么)。默认情况下，当IIS达到某个限制时，它会执行recycle+the+process，但它也会启动一个新的请求，并对所有传入的请求进行“阶段处理”，直到旧的请求未被使用为止，以便最大限度地减少中断。|3326984|我还写了一个小的c#类，它在正常情况下会keep+your+ASP.NET+application+alive+(alternate+archived+version)。由于它在应用程序中运行，显然它不能阻止IIS或其他任何东西显式地终止进程，但它将使应用程序保持“热”，例如，应用程序永远不会空闲足够长的时间，以便IIS决定关闭它。|3326985|如果您无法直接控制您的IIS配置(例如，共享主机)，最好的办法是让一个小型应用程序在单独的系统上运行-例如，一个始终在线的工作站-该系统每x分钟访问您的站点一次，以防止应用程序池超时。没什么特别的--控制台应用程序中一个简单的WebRequest和一个while()循环就可以了。|3326986|entityMap|0|LINK|mutability|MUTABLE|url|http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/29f53968-0115-451f-b26d-5ad58d87b5d1.mspx?mfr=true|1|http://www.odetocode.com/articles/305.aspx|2|http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/24e3c22e-79a9-4f07-a407-dbd0e7f35432.mspx?mfr=true|3|http://www.rexmorgan.net/journal/fixing_aspnet_ldquokeep|4|http://web.archive.org/web/20100213092317/http://www.rexmorgan.net/journal/fixing_aspnet_ldquokeep|5|http://msdn.microsoft.com/en-us/library/system.net.webrequest.aspx^0|1|4|0|1|4|0|N|E|0|16|9|1|2S|J|2|0|K|Z|3|1L|Q|4|0|35|A|5|0^^$0|@$1|2|3|4|5|6|7|15|8|@$9|16|A|17|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|18|8|@$9|19|A|1A|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1B|8|@]|D|@$9|1C|A|1D|1|1E]|$9|1F|A|1G|1|1H]|$9|1I|A|1J|1|1K]]|E|$]]|$1|J|3|K|5|6|7|1L|8|@]|D|@$9|1M|A|1N|1|1O]|$9|1P|A|1Q|1|1R]]|E|$]]|$1|L|3|M|5|6|7|1S|8|@]|D|@$9|1T|A|1U|1|1V]]|E|$]]|$1|N|3|-4|5|6|7|1W|8|@]|D|@]|E|$]]]|O|$P|$5|Q|R|S|E|$T|U]]|V|$5|Q|R|S|E|$T|W]]|X|$5|Q|R|S|E|$T|Y]]|Z|$5|Q|R|S|E|$T|10]]|11|$5|Q|R|S|E|$T|12]]|13|$5|Q|R|S|E|$T|14]]]]

In IIS 6, go to the Application Pools section, and right-click > Properties on the pool which hosts the ASP.NET application in question. Go to the Performance tab and uncheck "Shutdown worker processes after being idle for:"

In IIS 7, go to the Connections pane and find Application Pools, and select Advanced Settings for the pool which hosts your application. Find the "Idle Timeout" property and set it to "0" (this disables it).

The default is 20 minutes of inactivity. By unchecking the box, once your <a href="http://www.odetocode.com/articles/305.aspx" rel="noreferrer">AppDomain</a> is loaded by the <a href="http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/29f53968-0115-451f-b26d-5ad58d87b5d1.mspx?mfr=true" rel="noreferrer">worker process</a>, it will never die (unless you kill the process or something of course). By default, IIS will <a href="http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/24e3c22e-79a9-4f07-a407-dbd0e7f35432.mspx?mfr=true" rel="noreferrer">recycle the process</a> when it reaches some limit, such as a memory cap, but it will also start a new one and "phase over" all incoming requests until the old one is unused, so as to minimize disruption.

I've also written a small c# class which will <a href="http://www.rexmorgan.net/journal/fixing_aspnet_ldquokeep" rel="noreferrer">keep your ASP.NET application alive</a> (<a href="http://web.archive.org/web/20100213092317/http://www.rexmorgan.net/journal/fixing_aspnet_ldquokeep" rel="noreferrer">alternate archived version</a>) under normal circumstances. Since it runs within the application, obviously it can't stop IIS or anything else from explicitly killing the process, but it will keep the application "hot", e.g. the app will never go idle long enough for IIS to decide to shut it off.

If you do not have direct control over your IIS configuration (shared host, for example) your best bet is to have a small application running on a separate system - say, an always-on workstation - which hits your site every x minutes to keep the application pool from timing out. Nothing fancy - a simple <a href="http://msdn.microsoft.com/en-us/library/system.net.webrequest.aspx" rel="noreferrer">WebRequest</a> and a while() loop in a console application will do.

blocks|key|342244|text|我写了一个小的C#控制台应用程序，通过windows任务调度程序让我的4个站点每10分钟保持一次活动。生活再次变得美好起来。我们不会在凌晨2点到5点运行应用程序，这样服务器就可以清理内存，如果这很重要的话。对于我们的网站来说，几乎没有人在这些时间里工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|342245|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I wrote a little C# console application that keeps my 4 sites alive every 10 mins via windows task scheduler. Life is once again good. We do not run the app from 2-5am just so the serves can do any cleanups of memory, if it even matters. for our sites there is rarely anyone on at those hours anyway.

blocks|key|3114206|text|ASP+.net的优点之一是可以创建对象的静态(共享)实例。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3114207|为了避免外部进程的必要性，您可以(根据示例)在global.asax中创建一个静态计时器，它使用一个简单的WebRequest调用域上的一个页面。通过这种方式，站点将自己保持活动状态，直到完成池的手动重置。|3114208|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

One of the advantages of ASP .net is the posibility to create static (shared) instances of objects.

To avoid the necessity of an external process you can create an static timer in (per example) global.asax which calls for a page on the domain with a simple WebRequest. On this way the site keeps alive himself until a manual reset of the pool is done.

Scenario: I've an n-Tier enterprise ASP.NET application deployed using Web Deployment Projects. All tiers produce independent assemblies that is consumed by the ASP.NET application.

Problem: When I run the app. for the first time after deployment it takes lot of time to load dependent assemblies in memory. But once loaded its lighting fast app. In case if there are no users accessing the app, IIS unloads the assemblies from the memory and when a user tried to access the app on a later instance it goes on loading all the assemblies once again taking the same amount of time to load as it takes to do so for the first time.

I'm looking for a solution that enables me to keep my assemblies loaded into memory persistently overriding the volatile nature of assemblies towards memory residency.

Or any other solution that lets my users happily use the app resolving the mentioned problem.

How to keep ASP.NET assemblies in AppDomain alive?

服务器

场景: Web我有一个使用部署项目部署的n层企业ASP.NET应用程序。所有层都会生成供ASP.NET应用程序使用的独立程序集。问题:运行应用程序时出现。在部署之后，第一次在内存中加载依赖程序集需要花费大量时间。但一旦加载了它的快速照明应用程序。如果没有用户访问应用程序，IIS将从内存中卸载程序集，当用户尝试在以后的实...

问如何使AppDomain中的ASP.NET程序集保持活动状态？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使AppDomain中的ASP.NET程序集保持活动状态？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使AppDomain中的ASP.NET程序集保持活动状态？
EN