
April 30th, 2000, 01:36 AM
|
|
Contributing User
|
|
Join Date: Dec 2002
Posts: 14,575
  
Time spent in forums: < 1 sec
Reputation Power: 22
|
|
|
<i><b>Originally posted by : Barry</b></i><br />Your application timeout may be set to infinity.<br />Your session timeout may be set to infinity.<br />You may not be closing your sql recordsets after you use them.<br />Your object(s) may not be cleaning up.<br /><br />Try setting you application.timeout and session.timeout (registry settings in IIS) and make sure that you do a <br />recordset.close<br />set recordset = nothing<br />for every recordset you are creating.<br /><br /><br /><br />------------<br />Craig Coomber at 4/26/2000 9:06:40 AM<br /><br />Hi,<br /><br />I'm in a project just now using NT4 SP6a, IIS4 and ASP2 linked to local SQL server 7. We are experiencing a problem where the server (IIS) is caching any object even after they have been cleared. Eventually NT throws up the "low on virtual memory" moan message and the only way to clear it is to stop IIS. Then memory usage drops back like a stone.<br /><br />We've gone through the settings removing all options to cache everywhere but to no avail! Is this a common problem - have I overlooked something simple or do I need to throw in the towl???<br /><br />Cheers,<br /><br />Craig. <br />
|