Hi,
There still has not been a response. Does anyone have a suggestion please how
to clear the entire cache right now? And is it wrong to simply do
cache.remove(/)? If so why is it wrong, will memory not be freed up or
something like that? And why would the eviction class log these as
Actually, I traced these errors to consistenly happen after I do the following:
| cache.remove(/);
|
to remove all the contents of the cache. Is this in effect not a legal thing
to do, since I get those eviction errors afterward? If it is not, what is the
proper way to clear the
I am just curious why do you need to turn on eviction policy using Hibernate.
Isn't Hibernate has its own policy or I am mistaken? I will need to double
check this with Gavin.
Second of all, we are planning to provide an API that can clean up the whoe
cache content so you dont need to do it
Ok, just check with Gavin. Hibernate leaves the underlying cache to evict the
nodes. So it is kosher. But question is why do you need to clean up the whole
tree while turning on eviction though?
-Ben
View the original post :
Thanks for the answer Ben. In my application, I have certain data that
periodically gets loaded into the database by a different app, a batch load
process. I would like to clear my cache after this load process, so that a new
database load is forced and the new data would be used, rather than
