W3WP.EXE Memory consumption spiralling upwards

Our client app is basically a 'plug-in' OCX that is called by host systems and is used in call-centre environments to handle scripted dialogs with telephone callers.

At some point, the host instucts the OCX to launch a modal browser window. This then enters a succession of remote scripting calls to the server (running ASP plus VB DLLs) to conduct the question and answer session then in conclusion sets a Status inside a SQL Server database.

Meanwhile, the OCX merrily polls (yeek) the server at at 0.5 second intervals by calling an ASP page, waiting for a status change at which point it gathers all it needs from the database to return to the calling host.

For just about every ASP page loaded on the server, we late bind via a CreateObject("Msxml2.DOMDocument") and load an XML configuration document that drives the behaviour of the application.

Not your best architecture, but anyway...

Whilst the polling is underway, W3WP.EXE's memory utilisation reapidly increases in about 15KB chunks, roughly the size of the XML config document plus some overhead. This is clearly the case; depositing a load of dummy XML in the file is reflected by bigger chunks.

As you can imagine, this goes on until memory consumption gets silly then CPU starts to rise and eventually everything collapses. Until I am sure there is no alternative, I want to avoid recycling worker processes for the App Pool etc. I'd really like to avoid interruption of the often long conversations operators have with callers.

Once the OCX stops polling, memory is returned but very slowly and never all of it. Through code examination and other tests, we are fairly sure that there are no leaks in the application, well, certainly not on the scale witnessed.

I am aware of http://support.microsoft.com/kb/304227 but as our website doesn't run on dedicated servers I need to be certain this won't impact others.

Is MSXML caching like mad, is there any way to control this or can anyone give me deeper insight into what's going on?,

This is all under II6.0 on Server 2003 SP1.
LVL 1
Trevor HelpsTechnical DirectorAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Dave_DietzCommented:
It's not caching - you simply have a big pile of DOMDocument objects sitting around in memory until Garbage Collection can happen.  

Since you are seeing polling activity every .5 seconds from *each* client you likely aren't allowing the Garbage Collection to take place - something in the collection scheduling algorythm sees the high traffic and waits for a better time to collect.

Making the registry change may lessen the impact of the issue but it will affect any other applciations that use the same version of MSXML as the one you configure in the registry, but it will not likely be affecting them in a negative way.

Dave Dietz
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Trevor HelpsTechnical DirectorAuthor Commented:
I've implemented the registry change and we are currently monitoring activity. First signs are promising although it's hard to tell as, with the serious impact this was having, we have also simultaneously rationalised the polling activity.
0
Trevor HelpsTechnical DirectorAuthor Commented:
With large numbers of users and the high level of polling activity PLUS the discovery that an OCX was not being destroyed after use by the host application meant that each transaction left a process polling in the background. I saw polling levels at 155 per second - 'amazing that the server coped at all!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft IIS Web Server

From novice to tech pro — start learning today.