[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-3769) Enabling jmx statistics cause OOM

[Josh Moore (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41858#action_41858 ] 

Josh Moore commented on HHH-3769:
---------------------------------

For cases where turning off just query statistics is acceptable, allowing the configuration of a org.hibernate.stat.Statistics implementation would be useful. I'm currently patching our jars to use a `ConcurrentStatisticsImpl` which does not collect query stats. An option to disable just the query stats (setQueryStatisticsEnabled) would also work, but would be more invasive with changes being needed in QueryTranslatorImpl, Loader and QueryLoader. Nevertheless, to prevent unbounded growth for unsuspecting users, some form of cap on the size of the maps in that statitics implementations may be necessary.

> Enabling jmx statistics cause OOM
> ---------------------------------
>
>                 Key: HHH-3769
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3769
>             Project: Hibernate Core
>          Issue Type: Bug
>    Affects Versions: 3.2.0.ga
>            Reporter: Sid
>
> It looks like when org.hibernate.jmx.StatisticsService.statisticsEnabled=true all query strings get logged to org.hibernate.stat.StatisticsImpl.queryStatistics.
> There is a clear method in org.hibernate.stat.StatisticsImpl that reset all statistics but i don't see this method being called other than when some one calls org.hibernate.jmx.StatisticsService.clear()
> As queryStatistics is a HasMap this will causes OOM.

-- 
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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira