Terracotta Discussion Forums (LEGACY READ-ONLY ARCHIVE)

I have defined a few blocking-caches to overcome the Thundering Herd problem where many threads try to retrieve the same key from a cache and realize there is no value to it yet...

However, under BEA WebLogic10, I experience many hogging threads which will eventually turn into stuck threads with the bad effect that WLS allocates more threads for its thread-pool, although I have set a timeout to 500ms to prevent an endless wait to the cache.

After taking a thread-dump I noticed that the problem was caused by cache.put().
However, I have no idea on how to fix this problem. The only way I could solve it was by using non-blocking caches which dont help with the Thundering Herd problem

Can anybody point me in the right direction (using ehcache 2.0.1)?

Are you using the BlockingCache from Ehcache or your own?

I am using the CachingFilter base class which turns my regular cache via the cecorator automatically into a BlockingCache.

So are you saying that n requests come in for the same page. The page does not exist. With the web caching the first request will do the work. The other threads will block.

Now, this is correct. The idea is to avoid the work of each request.

You can control the number of threads that accumulate by setting a timeout which it sounds like you have done.

If this is correct then the web caching is already doing what it is supposed to.
Or are you saying there is a bug? i.e. the cache should not stop at cache.put(). The BlockingCache will hold threads at cache.get()