second-level-cache

问题 I would like to clarify some points regarding the secondary level cache of hibernate. The point to clarify is, will the HQL queries always hit the database (at least for getting ids). Consider we have entities class Customer { long id; // Primary key String name; set <Address> addressList; // One to many relationship } class Address{ long id; // Primary key String houseName; } The database table for the Address has a foreign key reference to the Customer (id) to support one to many

问题 I would like to clarify some points regarding the secondary level cache of hibernate. The point to clarify is, will the HQL queries always hit the database (at least for getting ids). Consider we have entities class Customer { long id; // Primary key String name; set <Address> addressList; // One to many relationship } class Address{ long id; // Primary key String houseName; } The database table for the Address has a foreign key reference to the Customer (id) to support one to many

问题 What is the best query strategy and the best configuration for my entities when the second level cache is activated. For example I have two entities User and Group with these relations : One User to Many Group : the groups owned by the user. Here a collection of Group in the User class and a User attribute (the owner) in the Group class. Many User to Many Group with attributes (status, date etc.) : the members of the groups. Because of the additionnals attibutes there is a specific class to

问题 In my grails application, I want to display all the current entries of the second-level cache from all regions . My code is as following : def getCacheStats() { StatisticsImpl stats = sessionFactory.statistics for (regionName in stats.secondLevelCacheRegionNames) { log.debug stats.getSecondLevelCacheStatistics(regionName).entries } } However everything works fine as long as the region name is not org.hibernate.cache.StandardQueryCache (region used for Query Cache). In that case, an exception

问题 In my grails application, I want to display all the current entries of the second-level cache from all regions . My code is as following : def getCacheStats() { StatisticsImpl stats = sessionFactory.statistics for (regionName in stats.secondLevelCacheRegionNames) { log.debug stats.getSecondLevelCacheStatistics(regionName).entries } } However everything works fine as long as the region name is not org.hibernate.cache.StandardQueryCache (region used for Query Cache). In that case, an exception

问题 I experience the following apparently undocumented issue, and I want to understand if I did something wrong Did anyone encounter the same issue? Is it really not documented anywhere? or did I miss something? The behavior is this Assume the following mapping <class name="org.sample.Foo" table="foo"> ... <many-to-one name="bar" class="org.sample.Bar"/> </class> <class name="org.sample.Bar" table="bar" lazy="false"> ... </class> First, as a background, Hibernate default value for the fetch

问题 The title obviously states it : I can't make the second-level cache work for JPA2/Hibernate 3.6.3. I've been trying many a hack to make it work. But I'm only succeeding in having the query cache working. Although Hibernate creates the caches (name of the instance), they're ignored. Even misses are not registered. Maybe it's a version incompatibility. I've tried some others with no result. And I don't feel up to the task anymore to try all permutations. :-P I'm asking the question here as some

问题 I'm getting following warning and I have no idea what to do about it. There is about 80000 entries that write this warning into catalina.out log file in tomcat every time the bannedIPs are getting updated: WARNING: Cache package.BannedIP Key package.BannedIP#73121 Lockable : null A soft-locked cache entry was expired by the underlying Ehcache. If this happens regularly you should consider increasing the cache timeouts and/or capacity limits Dec 16, 2010 10:00:53 PM net.sf.ehcache.hibernate

问题 Our Java application has about 100 classes mapped to a database (SQL Server or MySQL). We are using Hibernate as our ORM (with XML mapping files). We specify FOREIGN KEY constraints in our database schema. Most of our FOREIGN KEY constraints also specify ON DELETE CASCADE . We've recently started enabling Hibernate 2nd level caching (for popular entities and collections) to mitigate some performance problems. Performance has improved since we enabled the 2nd level cache. However we've also

问题 The NHibernate documentation and the book NHibernate In Action state that the cache provider NHibernate.Cache.HashtableCacheProvider is not intended for production use. However, I could not find a reason for this. Does anyone know the reason? 回答1: Because it doesn't support any kind of reasonable caching semantics (first example that comes to mind: timeouts), and it basically grows indefinitely. It's intended for testing only, as it just provides the simplest possible implementation of a