]
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: