C# ASP.NET page cache getting removed too soon

[baileyjames]

Oh Wise Ones - I need your help. Does anyone know what I can troubleshoot to see why an IIS 6.0 server (not clustered) will not hold this cache for the required 16 hours? It runs fine on our dev server and on my dev box.

_callingPage.Cache.Insert("SAPDS_Cache", ds, null, DateTime.Now.AddHours(16), System.Web.Caching.Cache.NoSlidingExpiration, System.Web.Caching.CacheItemPriority.NotRemovable, RemovedCallback);

The async callback (removedcallback) tells me the cache name with the reason being "removed".

Real bummer, users trying to test are tweaked.

[Plater]

Doesn't:
System.Web.Caching.Cache.NoSlidingExpiration,

mean that it should ignore future cache updates to that object and continue with the first cache statement? So if you load the page it goes "16 hours from now, expire" and every future load of that page will ignore the cache statements until it expires?

Also, unles you have a proxy server, caching is done on the client end, not the server end.

[baileyjames]

Actually this is asp.net cache and it's server side. There are two ways to configure the page.cache.insert statement, one is with sliding cache and the other is the way I did it, which expires at a point in time. I should note the server has plenty of memory so It's not garbage collecting, just removing it for some reason.

[baileyjames]

I figured this out. In IIS 6.0 the application pools can be configured to "clean up" worker threads. Well, that is exactly what it was doing. Right click on the application pool running your site, choose the performance tab, clear the checkbox for idle timeout or bump up the minutes to something you think appropriate for memory consumption by your site. You will need to be aware of how much memory is available on the box etc...