Clark Chang wrote:
Thanks for the reply. I did read the Jira issue about the timeout as you mentioned. Actually, We tested to leave the session open and garbage collect all the associated resources at the client side (hence should be the session itself), but it seems that the CacheManager still keep those extra caches related to that session.
the CacheManager only keeps weak references to the caches. there must be some other instance holding hard references to the cache.
regards marcel
