EHC ❯ Something wrong with the display for timestamp cache
-
Bug
-
Status: Closed
-
3 Minor
-
Resolution: Fixed
-
-
-
alexsnaps
-
Reporter: tgautier
-
February 27, 2010
-
0
-
Watchers: 0
-
July 27, 2012
-
September 27, 2011
Attachments
Description
When I look at the timestamp cache statistics in the hibernate/second-level-cache page, I see that there are no misses for o.h.c.UpdateTimestampsCache (see attached screenshot).
Yet, when I look at the same cache in the ehcache pane, then I see that there ARE misses. (See attached screenshot)
Comments
Chris Dennis 2010-03-02
Steve Harris 2010-03-02
Snaps has had some success getting patches into hibernate in the past. Maybe he has an idea.
Alexander Snaps 2010-03-03
I certainly think that providing the bug report _and_ the patch will raise our chances. I’ll be investigating how critical these guys see it. And also look into how hard it is to provide the said patch…
Fiona OShea 2010-03-03
Assigning to Alex based on his comment:
Fiona OShea 2010-03-19
find related Dev console issue
Fiona OShea 2010-03-19
assigning back to Alex to see if we can get the patch checked into Hibernate. We will not be showing this stat in the dev console so it is not critical right now.
Alexander Snaps 2010-06-21
I created this in their JIRA, http://opensource.atlassian.com/projects/hibernate/browse/HHH-5326 and launched a couple of alternative paths, will see whether it makes sense. The patch seems pretty easy to implement…
Alexander Snaps 2011-09-25
Fixed it again in 4.0, sent a pull request… We’ll see. If that isn’t happening, this will be a “Won’t fix” https://github.com/hibernate/hibernate-core/pull/171
Alexander Snaps 2011-09-27
Fixed for Hibernate 4.0
Hibernate 3.3.2 and probably all other versions of Hibernate don’t ever update the SecondLevelCacheStatistics object for the UpdateTimestampsCache. This means the numbers in the Hibernate/Second-Level-Cache page in the dev-console for hits, misses and puts on the UpdateTimestampsCache will always be zero. We could think about submitting this as a bug to the Hibernate developers although what our chances of it getting fixed are I don’t know.