Application Pool crashing due to excesive memory use or ASP error - ASP problem

Application Pool crashing due to excesive memory use or ASP error - ASP problem

Post by » Sat, 08 Nov 2008 22:47:00


I have a web site on a shared server (Win2003) and occasionally the site
goes down with a message "Service Unavailable" The ISP says there must be a
problem with the ASP content and excessive use of the Application Pool is
causing the problem

I can't find the cause but wonder if putting

<%Session.Abandon%>

and /or

<%Session.Contents.RemoveAll()%>

on the DB output pages will help to clear the excessive memory usage???

Any ideas???

Thanks
M
 
 
 

Application Pool crashing due to excesive memory use or ASP error - ASP problem

Post by Adrienne B » Sat, 08 Nov 2008 23:41:28

Gazing into my crystal ball I observed "mett << XXXX@XXXXX.COM >> writing in

>> I have a web site on a shared server (Win2003) and occasionally the >> site goes down with a message "Service Unavailable" The ISP says there >> must be a problem with the ASP content and excessive use of the >> Application Pool is causing the problem >> >> I can't find the cause but wonder if putting >> ><<%Session.Abandon>> >> >> and /or >> ><<%Session.Contents.RemoveAll()>> >> >> on the DB output pages will help to clear the excessive memory >> usage??? >> >> Any ideas??? >> >> Thanks >> M >> >> >> >> >>

Are you closing all record sets and closing the connection to the db?
For example I use on every page:
<
 
 
 

Application Pool crashing due to excesive memory use or ASP error - ASP problem

Post by Anthony Jo » Sun, 09 Nov 2008 19:17:11


>>I have a web site on a shared server (Win2003) and occasionally the site >>goes down with a message "Service Unavailable" The ISP says there must be a >>problem with the ASP content and excessive use of the Application Pool is >>causing the problem >> >> I can't find the cause but wonder if putting >> >><<%Session.Abandon>> >> >> and /or >> >><<%Session.Contents.RemoveAll()>> >> >> on the DB output pages will help to clear the excessive memory usage??? >> >> Any ideas??? >>

Are you using the Session object at all?
If so what for? How much data are you storing in the session object

Are you using the Application object at all?
If so what for? How much data are you storing in the application object?

How many distinct clients are actively hitting your site?

If you believe that you have too many session objects lying around unused
then a quick fix would be to reduce the session timeout on the site a
little.

Do you use thirdparty COM DLLs in you app (e.g., things other than the
typical ADODB and MSXML components)?

Are you storing COM objects in the Application or Session object?

--
Anthony Jones - MVP ASP/ASP.NET