Memory leak in JBoss AS / Hibernate JPA integration --------------------------------------------------- Key: WFLY-2593 URL: https://issues.jboss.org/browse/WFLY-2593 Project: WildFly Issue Type: Bug Security Level: Public(Everyone can see) Components: JPA / Hibernate Affects Versions: No Release Environment: JBoss 7.1.1 JBoss EAP 6.2 beta Reporter: Michael Kozak Assignee: Scott Marlow Priority: Critical Fix For: No Release Attachments: jmxp.ear.ear, jmxp.tar.gz The leak exists in AS integration code with Hibernate JPA. When a persistence unit is deployed which has 2nd level cache and statistics enabled each query for "query-cache" elements produces new elements. The issue lies in org.jboss.as.jpa.hibernate4.management.HibernateStatisticsResource. getQueryNames() method requests query names from Hibernate and applies QueryName.queryName(query).getDisplayName() to change names. Then for all queries hasQuery() is called which invokes stats.getQueryStatistics(). Within this method Hibernate creates a new object to track the statistics because the name is not found. Possible solution is to reverse the work done by getDisplayName() but I'm not sure if it's the right thing to do. This issue arised when we deployed jmxproxy application which was queried from Zabbix installation. For some MBean queries the implementation visits all MBeans deployed on the server. This kills the JVM after about 7 days.