MACROMEDIA COLFUSION MX 7-CFML Guía de usuario descargar pdf (Pagina 42)

BlueDragon 7.1: Deploying CFML on ASP.NET and the Microsoft .NET Framework 37

Still another approach would be to leverage one of the many automatic means built into .NET for

restarting a web application (discussed in section 7.1.2). For instance, if an application’s

web.config file is edited, that will restart the application.

7.1.2 Automatic Stopping/Restarting of .NET Web Applications

It’s important to be aware that the .NET Framework itself will stop (unload) web applications

automatically under various conditions. These can be very useful in preventing ongoing error sit-

uations, but their impact can be unexpected (such as the impact on sessions in section 7.1.3 or the

speed to restart applications as in section 7.1.4), so it’s important to know what these conditions

are.

The first set of conditions are generally quite beneficial. The .NET framework has various built-

in limiters, where if conditions are detected that may create instability in the .NET application,

the framework will restart the application.

• If any of several .NET-specific resource limiter settings are exceeded, as set in the

<processModel> element in the machine.config, a given application will be un-

loaded. These settings (including the percentage of memory used, the number of requests

served, etc.) are inherited by all .NET applications. For more information, see section

8.3.2.

• On Windows 2003, when not using IIS5 isolation mode (which is not used by default),

these <processModel> elements are ignored and instead the settings in Application

Pools

in IIS manager are used and set the limiters

The second set of conditions which can cause application restarts are generally more unexpected

and not completely documented by Microsoft. You should be aware of these, as your actions

may cause the application restart unexpectedly. Our experience so far has found that .NET will

stop web applications (leaving them ready to restart on the next request) under the following

conditions.

• If a directory within a given web application is renamed or deleted, or a new one is

created, that application will be unloaded

• If changes are made to files in the bin directory of a given web app, or a subdirectory

of that directory, that application will be unloaded

• If a single ASP.NET file (aspx, asmx, etc.) is edited and therefore recompiled more than

20 times since an application has been loaded, that application will be unloaded. The

number is set in the xml element within machine.config named

numRecompilesBeforeApprestart. This setting does not apply to CFML pages.

• If the machine.config file for the server is edited and saved (even if no change is

made), all .NET applications for that server will be unloaded.

• If the web.config, or global.asax file in a given web application root directory is

edited and saved (even if no change is made), that application will be unloaded

1 2 ... 37 38 39 40 41 42 43 44 45 46 47 ... 55 56

Sin comentarios

MACROMEDIA COLFUSION MX 7-CFML Guía de usuario Pagina 42