C# HttpRuntime.Cache.Insert() Not holding cached value

I’m trying to cache a price value using HttpRuntime.Cache.Insert(), but only appears to hold the value for a couple hours or something before clearing it out. What am I doing wrong? I want the value to stay in cache for 3 days.

HttpRuntime.Cache.Insert(CacheName, Price, null, DateTime.Now.AddDays(3), TimeSpan.Zero);


Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.

Method 1

Short answer

Your application pool or website is being shutdown too soon. Extend the idle timeout on the site, extend the application pool lifetime for the pool running the site. Raise the memory allocation and request limits.

Full answer

If you want to know when and why something is being removed from the cache, you need to log the item removal using the CacheItemRemovedCallback option on the insertion… Then you can log the reason using the CacheItemRemovedReason argument. You can thus log the reason as one of the four listed reasons:

  1. Removed The item is removed from the cache by a Remove method call or by an Insert method call that specified the same key.
  2. Expired The item is removed from the cache because it expired.
  3. Underused The item is removed from the cache because the system removed it to free memory.
  4. DependencyChanged The item is removed from the cache because the cache dependency associated with it changed.

Typically, you will find Expired and Underused being the reasons for things that don’t have explict Remove calls made against the cache and don’t have dependencies.

You will likely find out, while tracing through this fun stuff, that your items are not being expired or underused. Rather, I suspect you’ll find that the AppDomain is getting unloaded.

One way this can happen due to the web.config (or bin directory, or .aspx, etc.) files getting changed. For more information as to when this occurs see the Application Restarts section of this page. When that happens, the currently pending requests are drained, the cache emptied, and the AppDomain unloaded. You can detect this situation by checking the AppDomain.IsFinalizingForUnload and logging that during the callback.

Another reason for the AppDomain to recycle is when IIS decides to recycle the AppPool for any of the reasons it has been configured with. Examples of that are xxx memory has been allocated over the lifetime, yyy seconds of runtime for the AppPool, ttt scheduled recycle time, or iiii idle time (no requests incoming). For further details check this article for IIS6 or this article for IIS7

Method 2

The Cache object doesn’t guarantee that it will hold onto cached objects at all, much less for the full amount of time that you suggest.

If you want to more strongly encourage it to do so, you can set CacheItemPriority.High or CacheItemPriority.NotRemovable when you insert an item into the Cache. With the default Normal priority, the runtime has a fairly aggressive policy of letting go of objects when memory pressure increases.

On top of that, by default the IIS AppPool will recycle once/day or so, which will clear everything in the Cache.

Method 3

The docs http://msdn.microsoft.com/en-us/library/4y13wyk9.aspx say that Cache.NoSlidingExpiration must be used if using an absolute expiration.

HttpRuntime.Cache.Insert(CacheName, Price, null, DateTime.Now.AddDays(3), Cache.NoSlidingExpiration);

this may not be your problem though, i just found that Cache.NoSlidingExpiration should be the same as TimeSpan.Zero.

Next i would check that your app pool isnt expiring and check how much cache you are using. If it’s a high traffic site using a lot of memory (ie memory cache) then it will expire cache items as the memory is needed for other things.

also check the last comment here http://bytes.com/topic/net/answers/717129-c-asp-net-page-cache-getting-removed-too-soon someone seems to have found a solution to your problem.

Method 4

Check the recycle time on your App Pool.

Method 5

By default, items added to the cache have no set expiration, so this is definitely something outside the cache. I agree with Josh, you should check the recycle time on your App Pool.

Check out this page to see an example of how you can add a delegate to let you know exactly when your item is being removed from the cache. This might help you in troubleshooting if it’s not your App Pool:



All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

0 0 votes
Article Rating
Notify of

Inline Feedbacks
View all comments
Would love your thoughts, please comment.x