second-level-cache

I defined a second level cache in my application using @Cache annotation I am using findById query, as the following: long id = 4; Company cmp = companyDAO.findById(id); Where Company is the object that I get from the DB. How can I check if the Company object came from the DB or from the cache? Try HitCount and/or MissCount API. Something like this..... int oldMissCount = sessionFactory.getStatistics().getSecondLevelCacheStatistics(rName).getMissCount(); int oldHitCount = sessionFactory.getStatistics().getSecondLevelCacheStatistics(rName).getHitCount(); long id = 4; Company cmp = companyDAO

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 started encountering ObjectNotFoundExceptions. It seems the ObjectNotFoundExceptions are occuring because

I have read that using hibernate's second level cache, it can improve applications performance by having less database hits for data / object retrieval. However, how does hibernate ensure that second level cache is up to date with the data in database. For, example: Suppose the below class is entity and persisted into the DB. @Entity class User { Id private int id; private String str; } Now, if we have enabled second level cache, I understand that if we open different sessions then each session will hit the second level cache for retrieving object value. Now, if data in database gets changes

I am using CodeProject's well known Open Session in View to handle NHibernate Sessions. Does it works well with Level 2 Cache ? Anyone has succeeded doing it? Should I use NH.Burrow instead? Any advice on l2 cache in asp.net best practices is appreciated. Edit: link to CodeProject's article: http://www.codeproject.com/KB/architecture/NHibernateBestPractices.aspx I use the Unit of Work pattern to handle my session. Then I create an HttpModule that implements a "Session Per Web Request" lifetime that works really well. My HttpModule starts a Unit of Work on the PreExecuteRequestHandler hook,

I'm using Hibernate second level cache in my application, for certain business reason I can't change the entity annotation any more . In my project, apart from changing the Database from Hibernate, there exist also other native SQL that do not go through Hibernate. Therefore, the Hibernate second-level cache data could be stale after database being updated from native SQL. That's why I want to disable the second-level cache for certain entities (programmatically or other way than changing annotation). Thanks in advance! Matej WARNING: As Jens Schauder noted, it is impossible to configure

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 attribute on a many-to-one relation should be " select ", this is at least what is documented (I'll add the