ConcurrentList | A thread-safe , lock-free implementation of the IList T

The problem I was encountering stems from how I query the database, and how I was using hibernate.cache.use_second_level_cache and hibernate.cache.use_query_cache simultaneously.

Second Level Cache (hibernate.cache.use_second_level_cache): The second level cache is an application level cache for storing entity data when queried via primary key.

Query Cache (hibernate.cache.use_query_cache): The query cache is a separate cache that stores query results only. (My code from in findAll_test is accessing this cache)

The Problem

The issue lies with overlapping cache entry expiry. If you enable both caches, their cached entity objects overlap and the expiry policy of the Second Level Cache ends will overriding the Query Cache. Setting entities to expire at anything below never will decouple the Query Cache from re-caching any entities when it expires, leading to the deadlock condition.

The Solution

Don't use both at the same time. This appears to be bug, because you should be able to specify separate cache locations to use both caches simultaneously, but doing so does not prevent the problem from occurring.

There may be a way to solve this problem and leave the second level cache enabled, but I did not find it after extensive testing.

See Hibernate Caching for more information.