Java Mailing List Archive

http://www.gg3721.com/

Home » Hibernate Issues List »

[hibernate-issues] [Hibernate-JIRA] Issue Comment Edited:
(HHH-7004) Query cache is getting weird after an update into a single
transaction

Anupam M (JIRA)

2012-01-27

Replies: Find Java Web Hosting

Author LoginPost Reply

  [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-7004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45280#comment-45280 ]

Romain Gonord edited comment on HHH-7004 at 1/27/12 8:23 AM:
-------------------------------------------------------------

Into org.hibernate.cache.spi.UpdateTimestampsCache, method preinvalidate, we have :
Long ts = region.nextTimestamp() + region.getTimeout();
Into isUpToDate method, we get the value back and store it into lastUpdate which is wrong because it's more expirationDate.
So then, to make it work the way it should, we have to set timeout for the region to 0.


   was (Author: astik):
  Into org.hibernate.cache.spi.UpdateTimestampsCache, method preinvalidate, we have :
Long ts = region.nextTimestamp() + region.getTimeout();
Into isUpToDate method, we get the value back and store it into lastUpdate which is wrong because it's more expirationDate.
So then, to make it work the way it should, we have to set timeout for the region to 0.
You can do it globally by setting net.sf.ehcache.hibernate.cache_lock_timeout to 0.

> Query cache is getting weird after an update into a single transaction
> ----------------------------------------------------------------------
>
>           Key: HHH-7004
>           URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-7004
>         Project: Hibernate ORM
>       Issue Type: Bug
>       Components: core
>   Affects Versions: 3.6.9, 4.0.1
>        Reporter: Romain Gonord
>      Attachments: testHibernateEhCache.tgz
>
>
> Hi all,
> I'm using hibernate 4.0.1 and I'm facing a strange behavior. I can reproduce it with hibernate 3.6.9.
> I have an entity (integer id, string label) with query cache and level2 cache activated.
> If I load this object by its label, i get one select in the log and every following getbylabel doesn't produce any select query.
> As soon as I modify my object (that leads to an update query), each time I call the getbylabel, i get a select.
> By activating hibernate log, i can see that there is something strange with cache timestamp, which lead me to the following bug report : https://hibernate.onjira.com/browse/HHH-5210.
> Any idea ?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

   
_______________________________________________
hibernate-issues mailing list
hibernate-issues@(protected)
https://lists.jboss.org/mailman/listinfo/hibernate-issues
©2008 gg3721.com - Jax Systems, LLC, U.S.A.