Hibernate second-level cache ehcache.xml, the cache setting for entities can't be read to HIbernate

Question

To make it clear and easy, I have two projects: 1. An Entity project where there are all the entity classes in this project. 2. An project that contains a main() function to run the application, My ehcache.xml is placed in the class path of this project.

My problem is: I can change the defaultCache element of ehcache.xml and I can see changes from the SQL log file. But I think the Hibernate only read my defaultCache element, because whatever I change in the cache element of a specific entity of ehcache.xml, there won't be any changes in the SQL log.

For example: If I set the maxElementsInMemory of defaultCache element to 0, whatever I set the maxElementsInMemory of the cache element of a entity to 100 or 0, there won't be any that entity cached in the second level cache. If I set the maxElementsInMemory of defaultCache element to 100, whatever I set the maxElementsInMemory of the cache element of a entity to 100 or 0, there are always be that entity cached in the second level cache.

So I think maybe the name attribute of the cache element of a entity is wrongly set and cannot be read from Hibernate?

This might be an issue with the Hibernate configuration. It would help if you could include the hibernate.cfg.xml (or hibernate.properties) file, as well as at least one Hibernate mapping file (or the Java class w/annotations). — Matt Solnit
– Matt Solnit, Commented Jun 2, 2009 at 18:14
Thank you, I found where my problem is. I'm using ehcache as cache provider. In the ehcache.xml,I think the defaultCache element is also used for ALL THE QueryCaches too, if I didn't set the standardQueryCache element. So it's not important whether or not I set the maxElementsInMemory of <cache name="business.entity.car"...> to "0", because all the QueryCache are using the defaultCache region. But setting the maxElementsInMemory of <cache name="business.entity.car"...> to "0" can definitely help to disable the sencond-level cache of that entity when using EntityManager.find() function. — Kewei Shang
– Kewei Shang, Commented Jun 3, 2009 at 7:39

Kewei Shang · Accepted Answer · 2009-06-05 16:52:13Z

1

I found where my problem is. I'm using ehcache as cache provider. In the ehcache.xml,I think the defaultCache element is also used for ALL THE QueryCaches too, if I didn't set the standardQueryCache element. So it's not important whether or not I set the maxElementsInMemory of to "0", because all the QueryCache are using the defaultCache region. But setting the maxElementsInMemory of to "0" can definitely help to disable the sencond-level cache of that entity when using EntityManager.find() function.

answered Jun 5, 2009 at 16:52

Kewei Shang

9833 gold badges12 silver badges27 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

aLearner · Accepted Answer · 2012-12-10 04:52:10Z

0

PLEASE, read the documentation. In case of maxElementsInMemory setting, a value of 0 has a special meaning - unlimited. So instead of getting no cache at all, you're caching everything.

edited Dec 10, 2012 at 4:52

aLearner

1,04715 silver badges30 bronze badges

answered Oct 11, 2010 at 15:18

Marcin Sciesinski

1

Collectives™ on Stack Overflow

Hibernate second-level cache ehcache.xml, the cache setting for entities can't be read to HIbernate

2 Answers 2

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related