8:31 p.m.
session.clear() is not effective when use_query_cache is true
-------------------------------------------------------------
Key: HHH-3195
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3195
Project: Hibernate3
Issue Type: Bug
Affects Versions: 3.2.6
Environment: 3.2.6.ga, MySQL5
Reporter: James Berry
As discussed in detail in http://forum.hibernate.org/viewtopic.php?t=944918, performing
many inserts while use_query_cache is enabled will eventually cause an out of memory
condition, even if the session is periodically flushed and cleared. That forum thread
describes a potential root cause for this problem. Nobody from the Hibernate team has
responded regarding the forum thread, even though it's been alive for three years
now!
Note that an answer to "disable the query cache" is not a good solution to the
problem, as we need the query cache elsewhere. If it were possible to disable the query
cache for a particular session, that would be fine, but I see no way do that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:41 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3195) session.clear() is not effective when use_query_cache is true
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3195?page=c...
]
Gail Badner commented on HHH-3195:
----------------------------------
By calling Session.setCacheMode( CacheMode.IGNORE ) on your session, the second-level
cache should be ignored, except to invalidate cache items when updates occur.
session.clear() is not effective when use_query_cache is true
-------------------------------------------------------------
Key: HHH-3195
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3195
Project: Hibernate3
Issue Type: Bug
Affects Versions: 3.2.6
Environment: 3.2.6.ga, MySQL5
Reporter: James Berry
As discussed in detail in http://forum.hibernate.org/viewtopic.php?t=944918, performing
many inserts while use_query_cache is enabled will eventually cause an out of memory
condition, even if the session is periodically flushed and cleared. That forum thread
describes a potential root cause for this problem. Nobody from the Hibernate team has
responded regarding the forum thread, even though it's been alive for three years
now!
Note that an answer to "disable the query cache" is not a good solution to the
problem, as we need the query cache elsewhere. If it were possible to disable the query
cache for a particular session, that would be fine, but I see no way do that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:47 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3195) session.clear() is not effective when use_query_cache is true
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3195?page=c...
]
James Berry commented on HHH-3195:
----------------------------------
Gail: yes, that's what one would thing, but that's not the case. That setting has
no effect on this case.
session.clear() is not effective when use_query_cache is true
-------------------------------------------------------------
Key: HHH-3195
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3195
Project: Hibernate3
Issue Type: Bug
Affects Versions: 3.2.6
Environment: 3.2.6.ga, MySQL5
Reporter: James Berry
As discussed in detail in http://forum.hibernate.org/viewtopic.php?t=944918, performing
many inserts while use_query_cache is enabled will eventually cause an out of memory
condition, even if the session is periodically flushed and cleared. That forum thread
describes a potential root cause for this problem. Nobody from the Hibernate team has
responded regarding the forum thread, even though it's been alive for three years
now!
Note that an answer to "disable the query cache" is not a good solution to the
problem, as we need the query cache elsewhere. If it were possible to disable the query
cache for a particular session, that would be fine, but I see no way do that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:53 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3195) session.clear() is not effective when use_query_cache is true
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3195?page=c...
]
Shawn Clowater commented on HHH-3195:
-------------------------------------
The problem isn't with the 2nd level cache it is with the ActionQueue that holds on to
all references for the after transaction processing.
session.clear() is not effective when use_query_cache is true
-------------------------------------------------------------
Key: HHH-3195
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3195
Project: Hibernate3
Issue Type: Bug
Affects Versions: 3.2.6
Environment: 3.2.6.ga, MySQL5
Reporter: James Berry
As discussed in detail in http://forum.hibernate.org/viewtopic.php?t=944918, performing
many inserts while use_query_cache is enabled will eventually cause an out of memory
condition, even if the session is periodically flushed and cleared. That forum thread
describes a potential root cause for this problem. Nobody from the Hibernate team has
responded regarding the forum thread, even though it's been alive for three years
now!
Note that an answer to "disable the query cache" is not a good solution to the
problem, as we need the query cache elsewhere. If it were possible to disable the query
cache for a particular session, that would be fine, but I see no way do that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:02 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3195) session.clear() is not effective when use_query_cache is true
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3195?page=c...
]
Les Hazlewood commented on HHH-3195:
------------------------------------
Please vote for this issue if you wish it to be a priority!
session.clear() is not effective when use_query_cache is true
-------------------------------------------------------------
Key: HHH-3195
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3195
Project: Hibernate3
Issue Type: Bug
Affects Versions: 3.2.6
Environment: 3.2.6.ga, MySQL5
Reporter: James Berry
As discussed in detail in http://forum.hibernate.org/viewtopic.php?t=944918, performing
many inserts while use_query_cache is enabled will eventually cause an out of memory
condition, even if the session is periodically flushed and cleared. That forum thread
describes a potential root cause for this problem. Nobody from the Hibernate team has
responded regarding the forum thread, even though it's been alive for three years
now!
Note that an answer to "disable the query cache" is not a good solution to the
problem, as we need the query cache elsewhere. If it were possible to disable the query
cache for a particular session, that would be fine, but I see no way do that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:01 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3195) session.clear() is not effective when use_query_cache is true
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3195?page=c...
]
sam lewis commented on HHH-3195:
--------------------------------
As a temporary workaround I added this line after session.clear()
((SessionImpl)session).getActionQueue().executeActions()
It seems to work in my use case but I don't know if manually flushing the execute
queue is a good idea.
session.clear() is not effective when use_query_cache is true
-------------------------------------------------------------
Key: HHH-3195
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3195
Project: Hibernate Core
Issue Type: Bug
Affects Versions: 3.2.6
Environment: 3.2.6.ga, MySQL5
Reporter: James Berry
As discussed in detail in http://forum.hibernate.org/viewtopic.php?t=944918, performing
many inserts while use_query_cache is enabled will eventually cause an out of memory
condition, even if the session is periodically flushed and cleared. That forum thread
describes a potential root cause for this problem. Nobody from the Hibernate team has
responded regarding the forum thread, even though it's been alive for three years
now!
Note that an answer to "disable the query cache" is not a good solution to the
problem, as we need the query cache elsewhere. If it were possible to disable the query
cache for a particular session, that would be fine, but I see no way do that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:40 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3195) session.clear() is not effective when use_query_cache is true
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3195?page=c...
]
Chris Brown commented on HHH-3195:
----------------------------------
Sadly, calling executeActions does not cause the references to be released - if you put a
breakpoint in executeActions, you'll see that it is called on a regular flush anyway.
I have had success getting Hibernate to release the references by calling this after
session.clear():
((SessionImpl)session).getActionQueue().afterTransactionCompletion(true)
If you are only doing inserts I think this should be a fairly safe solution, because the
afterTransactionCompletion hook for an insert just updates the 2nd level cache, which you
should have disabled anyway.
The problem is due to the fact that the ActionQueue finds out whether the cache is enabled
by calling:
session.getFactory().getSettings().isQueryCacheEnabled()
It seems to me that this check should also take into account whether the second-level
cache is enabled, and the current cache mode of the session.
session.clear() is not effective when use_query_cache is true
-------------------------------------------------------------
Key: HHH-3195
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3195
Project: Hibernate Core
Issue Type: Bug
Affects Versions: 3.2.6
Environment: 3.2.6.ga, MySQL5
Reporter: James Berry
As discussed in detail in http://forum.hibernate.org/viewtopic.php?t=944918, performing
many inserts while use_query_cache is enabled will eventually cause an out of memory
condition, even if the session is periodically flushed and cleared. That forum thread
describes a potential root cause for this problem. Nobody from the Hibernate team has
responded regarding the forum thread, even though it's been alive for three years
now!
Note that an answer to "disable the query cache" is not a good solution to the
problem, as we need the query cache elsewhere. If it were possible to disable the query
cache for a particular session, that would be fine, but I see no way do that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:08 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3195) session.clear() is not effective when use_query_cache is true
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3195?page=c...
]
Chris Brown commented on HHH-3195:
----------------------------------
Further to my comment above, calling afterTransactionCompletion early is dangerous if you
are using a read-write cache: if your operation fails, causing the transaction to be
rolled back, the modified entities will still be committed to the cache, leaving it in a
corrupt state. However, if you are using a non-strict read-write cache (as I am) all that
happens is that the cache is invalidated, which doesn't matter so much.
The only non-cache related consequences of calling afterTransactionCompletion that I can
find from reading the source are related to the Hibernate search index. If you aren't
using Hibernate search, then that won't be an issue.
session.clear() is not effective when use_query_cache is true
-------------------------------------------------------------
Key: HHH-3195
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3195
Project: Hibernate Core
Issue Type: Bug
Affects Versions: 3.2.6
Environment: 3.2.6.ga, MySQL5
Reporter: James Berry
As discussed in detail in http://forum.hibernate.org/viewtopic.php?t=944918, performing
many inserts while use_query_cache is enabled will eventually cause an out of memory
condition, even if the session is periodically flushed and cleared. That forum thread
describes a potential root cause for this problem. Nobody from the Hibernate team has
responded regarding the forum thread, even though it's been alive for three years
now!
Note that an answer to "disable the query cache" is not a good solution to the
problem, as we need the query cache elsewhere. If it were possible to disable the query
cache for a particular session, that would be fine, but I see no way do that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:24 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3195) session.clear() is not effective when use_query_cache is true
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3195?page=c...
]
Strong Liu commented on HHH-3195:
---------------------------------
iirc, this is resolved (i don't know when), take a look of
https://github.com/hibernate/hibernate-core/blob/master/hibernate-core/sr...,
the ActionQuene does not hold reference anymore.
would you guys please confirm? (or am i missing anythign here?)
p.s. i just tried insert Integer.MAX_VALUE simple objects with query cache enabled, and no
OME
session.clear() is not effective when use_query_cache is true
-------------------------------------------------------------
Key: HHH-3195
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3195
Project: Hibernate Core
Issue Type: Bug
Affects Versions: 3.2.6
Environment: 3.2.6.ga, MySQL5
Reporter: James Berry
As discussed in detail in http://forum.hibernate.org/viewtopic.php?t=944918, performing
many inserts while use_query_cache is enabled will eventually cause an out of memory
condition, even if the session is periodically flushed and cleared. That forum thread
describes a potential root cause for this problem. Nobody from the Hibernate team has
responded regarding the forum thread, even though it's been alive for three years
now!
Note that an answer to "disable the query cache" is not a good solution to the
problem, as we need the query cache elsewhere. If it were possible to disable the query
cache for a particular session, that would be fine, but I see no way do that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:26 p.m.
New subject: [Hibernate-JIRA] Resolved: (HHH-3195) session.clear() is not effective when use_query_cache is true
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3195?page=c...
]
Strong Liu resolved HHH-3195.
-----------------------------
Assignee: Strong Liu
Resolution: Duplicate
duplicated by HHH-3028
session.clear() is not effective when use_query_cache is true
-------------------------------------------------------------
Key: HHH-3195
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3195
Project: Hibernate Core
Issue Type: Bug
Affects Versions: 3.2.6
Environment: 3.2.6.ga, MySQL5
Reporter: James Berry
Assignee: Strong Liu
As discussed in detail in http://forum.hibernate.org/viewtopic.php?t=944918, performing
many inserts while use_query_cache is enabled will eventually cause an out of memory
condition, even if the session is periodically flushed and cleared. That forum thread
describes a potential root cause for this problem. Nobody from the Hibernate team has
responded regarding the forum thread, even though it's been alive for three years
now!
Note that an answer to "disable the query cache" is not a good solution to the
problem, as we need the query cache elsewhere. If it were possible to disable the query
cache for a particular session, that would be fine, but I see no way do that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4705
days inactive
5888
days old
hibernate-issues@lists.jboss.org
9 comments
7 participants
participants (7)
-
Chris Brown (JIRA) -
Gail Badner (JIRA)
-
James Berry (JIRA)
-
Les Hazlewood (JIRA)
-
sam lewis (JIRA)
-
Shawn Clowater (JIRA)
-
Strong Liu (JIRA)