[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2431?page=c...
]
Eric Goff commented on HHH-2431:
--------------------------------
Of course, if one was using good database practice, one would be
using parameterized queries and not have this problem.
But an unbounded cache is also not a good POSA practice. :)
QueryPlanCache grows without bound. Eventually gets
OutOfMemoryException
--------------------------------------------------------------------------
Key: HHH-2431
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2431
Project: Hibernate3
Type: Bug
Components: core
Versions: 3.2.2
Environment: all versions, all platforms
Reporter: Eric Goff
Every time you execute a query, and that query does not match any existing queries
in the QueryPlanCache, that query is *always* added to the Query Plan Cache, along with
a lot of various antlr stuff.
There seems to be no way to control it.
Minimally, there should be some sort of heap of query plans where the
least used query plan is ejected when the cache reaches it max size.
The cache size should, of course, be user configurable.
--
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