I have an ASP (classic) application that works fine using IIS 5.0. When
using IIS 6.0 I have no problems when in "IIS 5.0 Isolation Mode", but when
IIS 6.0 is using "Worker process isolation mode" I get an "Out of memory"
error in one of my COM components when it is called from an ASP page. There
is no error being generated in an event log or from IIS, the only sign that
something has gone wrong is that the COM component reports that it
encountered an internal "Out of memory" error during processing (which at
that point involves getting some data from a database, analyzing it and
generating a chart image).
This particular COM component does tend to use a lot of memory - when I use
it in a standard windows application the task manager memory usage goes up
to around 26 MB at that point in the processing.
I'm guessing that the total memory available to my COM component when
running in "Worker process isolation mode" is less that that available in
"IIS 5.0 Isolation Mode".
Are there any adjustments that can be made to affect how much memory is made
available to my application when running in "Worker process isolation mode"?
Or, does anyone have any suggestions on how to get this application to run
in "Worker process isolation mode"?
>> Stay informed about: IIS 6.0 - Memory problem in "Worker process isolation mode"