[Hibernate-JIRA] Created: (HHH-7004) Query cache is getting weird after an update into a single transaction
4:06 a.m.
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: 4.0.1, 3.6.9
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
4:08 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-7004) Query cache is getting weird after an update into a single transaction
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-7004?page=c...
]
Romain Gonord commented on HHH-7004:
------------------------------------
I attached a full maven project that reproduce the behavior.
To see the description in action, just run the unit test and watch for the log.
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
8:22 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-7004) Query cache is getting weird after an update into a single transaction
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-7004?page=c...
]
Romain Gonord commented on HHH-7004:
------------------------------------
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
8:24 a.m.
New subject: [Hibernate-JIRA] Issue Comment Edited: (HHH-7004) Query cache is getting weird after an update into a single transaction
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-7004?page=c...
]
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
8:24 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-7004) Query cache is getting weird after an update into a single transaction
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-7004?page=c...
]
Romain Gonord commented on HHH-7004:
------------------------------------
For ehcache, 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
9:02 p.m.
New subject: [Hibernate-JIRA] Assigned: (HHH-7004) Query cache is getting weird after an update into a single transaction
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-7004?page=c...
]
Strong Liu reassigned HHH-7004:
-------------------------------
Assignee: Strong Liu
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
Assignee: Strong Liu
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
2:11 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-7004) Query cache is getting weird after an update into a single transaction
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-7004?page=c...
]
Strong Liu commented on HHH-7004:
---------------------------------
I would not think this is a _bug_ but an expected behavior.
since the data is being updated, so, it would be safer to hit DB instead of getting
steal/dirty data from cache.
to avoid this, try commit tx after the update
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
Assignee: Strong Liu
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
2:17 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-7004) Query cache is getting weird after an update into a single transaction
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-7004?page=c...
]
Romain Gonord commented on HHH-7004:
------------------------------------
I agree for the select following the update, but what about the next ones ?
The idea would be :
getBylabel -> put in cache version 1
update
getByLabel -> put in cache version 2
getByLabel -> get version 2 from cache
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
Assignee: Strong Liu
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
2:22 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-7004) Query cache is getting weird after an update into a single transaction
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-7004?page=c...
]
Strong Liu commented on HHH-7004:
---------------------------------
TX1: TX2:
getBylabel getBylabel
update getBylabel
getBylabel getBylabel
getBylabel getBylabel
rollback getBylabel
----------------------------------------------
query cache is a process scope cache, not transactional scope
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
Assignee: Strong Liu
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
2:22 a.m.
New subject: [Hibernate-JIRA] Issue Comment Edited: (HHH-7004) Query cache is getting weird after an update into a single transaction
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-7004?page=c...
]
Strong Liu edited comment on HHH-7004 at 1/30/12 2:22 AM:
----------------------------------------------------------
{code}
TX1: TX2:
getBylabel getBylabel
update getBylabel
getBylabel getBylabel
getBylabel getBylabel
rollback getBylabel
{code}
----------------------------------------------
query cache is a process scope cache, not transactional scope
was (Author: stliu):
TX1: TX2:
getBylabel getBylabel
update getBylabel
getBylabel getBylabel
getBylabel getBylabel
rollback getBylabel
----------------------------------------------
query cache is a process scope cache, not transactional scope
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
Assignee: Strong Liu
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
4:29 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-7004) Query cache is getting weird after an update into a single transaction
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-7004?page=c...
]
Philippe De Oliveira commented on HHH-7004:
-------------------------------------------
What seems awkward to me is that the timeout is used as a *bottom* limit for cache use.
Until you reach the timeout the cache is not used, then when you reached it, the cache is
used ! This is the opposite of a timeout behaviour !
If you change the test to use a timeout of 10 secs and then you introduce a pause of 12
sec between two getByLabel then the cache is used for the next call.
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
Assignee: Strong Liu
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
5179
days inactive
5182
days old
hibernate-issues@lists.jboss.org
10 comments
3 participants
participants (3)
-
Philippe De Oliveira (JIRA) -
Romain Gonord (JIRA)
-
Strong Liu (JIRA)