Things that should be done to help with stability:
- Keep applications in their own IIS pool
- Up external connections in machine.config
- pre-compile and sign applications
Keep applications in their own IIS pool
- open IIS manager, expand machine
IIS Create App Pool
- Right-click new Application Pool
Create App Pool Dialog
- Insert application Name, Select "use existing application pool as template" and "ASP.NEt v2.0", click OK
- Open Web Sites
- right click on Application, select properties
- Select Application Pool you created, and click OK
If there are issue with your application, you can change the properties of the application pool to limit memory, restart it.
Up external connections in machine.config
The maxconnection attribute in Machine.config limits the number of concurrent outbound calls.
Note This setting does not apply to local requests (requests that originate from ASP.NET applications on the same server as the Web service). The setting applies to outbound connections from the current computer, for example, to ASP.NET applications and Web services calling other remote Web services.
The default setting for maxconnection is two per connection group. For desktop applications that call Web services, two connections may be sufficient. For ASP.NET applications that call Web services, two is generally not enough. Change the maxconnection attribute from the default of 2 to (12 times the number of CPUs) as a starting point.
Monitoring ASP Net App pools
- Search for machine.config, (should be: [Root drive]:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG )
- insert a system.net block between system.data and system.web:
<add address="*" maxconnection="12"/>