|
Home > Archive > Commerce Server General > September 2004 > w3wp dying with 'out of memory' errors
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
w3wp dying with 'out of memory' errors
|
|
|
| Hi,
We have a bit of a problem with a couple of our servers falling over, and
throwing an 'Out of Memory' exception. It seems to happen when the w3wp
process takes up from 400 to 600 MB. After a bit of time - from 4min to a
few hours, the w3wp falls over and fails, taking the website down until
either the process is recycled or an iisreset is performed.
The symptoms are similar to the ones described by this fellow:
http://www.codecomments.com/asp/mes...GP09.phx.gbl%3E
The testing scripts that he has there work to simulate the exception, except
that the worker process isn't knocked over; if you create an out of memory
exception, the process still seems to serve up pages, and isn't too
bothered. Which leads me to believe that it's perhaps a related problem,
but not neccessarily the same thing.
Server specs
ASP .NETv1.1
windows server 2003
IIS 6.0
4GB of ram
*no database on this box - it's dedicated to just serving pages*
I have been able to alieviate it somewhat by giving the website it's own
application pool and setting it to use 3 worker processes and recycle when
memory reaches 350MB, but this is somewhat disruptive to the users of the
website, as their sessions seem to get abandoned sometimes, or they get a
'SERVER UNAVAILABLE' error.
I got the idea to split it up from this page:
http://dotnetjunkies.com/Newsgroups...1/29/41621.aspx
We tend to use lots of cached data - tables, sets, variables, etc.
Now my question is: Why does IIS fall over when using such a small memory
footprint? We have 4GB, yet w3wp can only use 400MB?
If anyone knows of any other sort of configuration or tips or hints it is
muchly appreciated.
Thanks,
Lance
| |
| Maria Quian [MSFT] 2004-09-25, 5:53 pm |
| Thank you for using Microsoft Newsgroups.
The only real way to determine the cause and the solution would be to use
IIS Crash/Hang Agent & IIS Dump.
http://www.microsoft.com/downloads/...aylang=en&famil
yid=01c4f89d-cc68-42ba-98d2-0c580437efcf&displaylang=en. You might need to
open an incident to have it analyzed but I am sure a support professional
can determine the source of the problem with the appropriate dump files.
Maria Quian
Microsoft Technical Support
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2002 Microsoft Corporation. All rights
reserved.
|
|
|
|
|