[hibernate-issues] [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. -- 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