N
Neil Stephens
We have an ASP.NET (VB) process that is creating a stringbuilder object
which is failing under a particular set of circumstances.
It runs fine on a few dozen servers except for one where an OOM exception
occurs. The size of the object is large, in the region of 10s of MBs and
limited to a single process at any one time.
The problem server is running Windows 2000 Advanced Server SP4 (with
terminal services) on an AMD Opteron processor with 4Gb of memory and .Net
is version 1.1. There is nothing else being run on the server. Physical
address extensions have been enabled.
Is it possible that there has been a limit placed on the amount of memory
that ASP.NET can use ? Any pointers to how we can trace the cause of the
issue ? We've monitored the usual memory counters and there's no obvious
memory leaks, although the aspnet_wp process never exceeds more than 400MB.
Thanks,
Neil Stephens,
Foresite Systems.
which is failing under a particular set of circumstances.
It runs fine on a few dozen servers except for one where an OOM exception
occurs. The size of the object is large, in the region of 10s of MBs and
limited to a single process at any one time.
The problem server is running Windows 2000 Advanced Server SP4 (with
terminal services) on an AMD Opteron processor with 4Gb of memory and .Net
is version 1.1. There is nothing else being run on the server. Physical
address extensions have been enabled.
Is it possible that there has been a limit placed on the amount of memory
that ASP.NET can use ? Any pointers to how we can trace the cause of the
issue ? We've monitored the usual memory counters and there's no obvious
memory leaks, although the aspnet_wp process never exceeds more than 400MB.
Thanks,
Neil Stephens,
Foresite Systems.