ASP.NET Worker Process Memory Growing

[Pablo Bianco SE]

Hi everyone, I am new in this group. I have a question and would like to have
some support.
A customer is experiencing memory problems with the asp.net worker process.
The have an application installed on Windows 2003 Server (IIS6). We the
application starts the worker process ocuppies about 70MB, but it keeps
growing gradually during users activity. In just few hours (about 4 hours) it
can reach 800 MB, making the application not being responsive and not
available. Despite we can set a recycling policy based on memory usage, this
temporary solutions was rejected by our customer.The session time out is set
to 20 minutes (default) and we consider that we are not abusing in the
session memory usage.
Does anyone know what can be happening and how to proceed?

More info about our application:
* asp.net, c# (all managed code)
* .net framework 1.1 with service pack1
* Windows 2003 Server with service pack
* Microsoft UIP (User interface process application block)
* NHibernate (ORM for data access)
* DAC2 (Data access framework)
* we hace a root application with subapplications (none of the
subapplications are marked as virtual applications in IIS)
* we dont use custom urls (url rewriting)
* we use reflection
* we use session in process state
* Oracle 9i or SQL2000 (of course only on of them)
Thanks a lot for you attention!
best regards,

-pablo

[John Timney \(MVP\)]

Get your customer to agree to a recycling policy while you investigate what
the root cause of the problem is. You really need to be doing memory
profiling if your at th stage where automatic app recycling dont solve your
issues.

A really useful article to help you get started.
http://blogs.msdn.com/ricom/archive/...10/279612.aspx

Regards

John Timney (MVP)
"Pablo Bianco SE" <Pablo Bianco [e-mail] in
message news:BE**********************************@microsof t.com...

Hi everyone, I am new in this group. I have a question and would like to
have
some support.
A customer is experiencing memory problems with the asp.net worker
process.
The have an application installed on Windows 2003 Server (IIS6). We the
application starts the worker process ocuppies about 70MB, but it keeps
growing gradually during users activity. In just few hours (about 4 hours)
it
can reach 800 MB, making the application not being responsive and not
available. Despite we can set a recycling policy based on memory usage,
this
temporary solutions was rejected by our customer.The session time out is
set
to 20 minutes (default) and we consider that we are not abusing in the
session memory usage.
Does anyone know what can be happening and how to proceed?

More info about our application:
* asp.net, c# (all managed code)
* .net framework 1.1 with service pack1
* Windows 2003 Server with service pack
* Microsoft UIP (User interface process application block)
* NHibernate (ORM for data access)
* DAC2 (Data access framework)
* we hace a root application with subapplications (none of the
subapplications are marked as virtual applications in IIS)
* we dont use custom urls (url rewriting)
* we use reflection
* we use session in process state
* Oracle 9i or SQL2000 (of course only on of them)
Thanks a lot for you attention!
best regards,

-pablo