Due to changes in Windows memory monitoring since Windows Vista/Server 2008, customers running the OASP .NET server module on an upgraded Windows environment could see memory violations which may eventually cause the web server to crash.
The following steps will provide a workaround and will also improve both stability and performance. Intermittent memory violations may still occur if the server is under high stress for a long duration, but this will not be sufficient to cause a service outage.
- Open Internet Information Services Manager
- Select “Application Pools”, right click on the application pool used by your website and select “Advanced Settings…”
- On the “Advanced Settings” popup dialog, set “Maximum Worker Processes” to 5. This will ensure the most stable environment under very heavy load.
Note: a lower number may work but this will depend on the server load and on your application.
- Ensure “Disabled Overlapped Recycle” is set to ‘False’
- Specify a “Maximum Request Limit” to ensure the worker process is recycled periodically.