Bug 1037636
Summary: | [GSS] (6.2.x) Memory leak in JBoss AS / Hibernate JPA integration | |||
---|---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Michal P <michal.pasierb> | |
Component: | JPA | Assignee: | Scott Marlow <smarlow> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Zbyněk Roubalík <zroubali> | |
Severity: | urgent | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 6.2.0 | CC: | cdewolf, fnasser, jason.greene, jawilson, jdoyle, lcosti, msimka, myarboro, smarlow, smumford | |
Target Milestone: | CR1 | |||
Target Release: | EAP 6.2.1 | |||
Hardware: | All | |||
OS: | All | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
A memory leak that occurred when checking the query cache statistics has been resolved in this release of JBoss EAP 6.
The leak occurred each time that jboss-cli was invoked to check the query cache. For example the following command would cause the leak:
----
./jboss-cli.sh --connect --command='/deployment=DeploymentName.ear/subdeployment=MyEjb.jar/subsystem=jpa/hibernate-persistence-unit=DeploymentName.ear\/MyEjb.jar#MyPersistenceUnit:read-children-resources(child-type=query-cache)'
----
An invalid query name was being used when checking the query cache statistics, which returned invalid results and also caused each invalid query name to be added to the Hibernate statistics. This release no longer uses an invalid query name when checking the query cache statistics.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1040733 (view as bug list) | Environment: | ||
Last Closed: | 2014-02-24 20:14:39 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 1040733 | |||
Bug Blocks: | 1027004 |
Description
Michal P
2013-12-03 14:16:31 UTC
Scott Marlow <scott.marlow> updated the status of jira WFLY-2593 to Resolved Scott Marlow <scott.marlow> made a comment on jira WFLY-2593 Cannot reproduce the leak in WildFly 8 and *should* be fixed in next EAP 6.x release (you could open a ticket with Red Hat support asking for the fix for your production environment). Scott Marlow <scott.marlow> updated the status of jira WFLY-2593 to Closed Michael Kozak <lklm> made a comment on jira WFLY-2593 Sorry Scott I didn't check the WildFly at all. I just assumed this issue tracker is for JBoss 7 AS too since the original space is closed. I already created an issue in Red Hat issue tracker. The link is available at this page in "Bugzilla References". I wonder how can I view the statistics in WildFly. I see there is no "hibernate-persistence-unit" under /deployment=jmxp.ear.ear/subdeployment=jmxp.ejb.jar/subsystem=jpa. Was the removal of this functionallity intended ? Scott Marlow <scott.marlow> made a comment on jira WFLY-2593 No need to apologize, this was an excellent bug report (+10 for providing a test case ready to be used). Also, your test case didn't work on WildFly right away, Brian had to fix WFLY-2609 first. So, you also helped us to find that. {quote} I wonder how can I view the statistics in WildFly. I see there is no "hibernate-persistence-unit" under /deployment=jmxp.ear.ear/subdeployment=jmxp.ejb.jar/subsystem=jpa. Was the removal of this functionallity intended ? {quote} This is the WFLY-2609 bug that you also helped me find! :-) Marking for inclusion in 6.2.1 release notes documentation. Requesting information about how this memory leak was resolved to complete the release notes draft started in the Doc Text field. Verified in 6.2.1.CP.CR1-patch A memory leak was fixed that occurred when checking the query cache statistics. The leak occurred each time that jboss-cli was invoked to check the query cache. For example the following command would cause the leak: ./jboss-cli.sh --connect --command='/deployment=DeploymentName.ear/subdeployment=MyEjb.jar/subsystem=jpa/hibernate-persistence-unit=DeploymentName.ear\/MyEjb.jar#MyPersistenceUnit:read-children-resources(child-type=query-cache)' Thanks for the new content Scott. I've replaced my draft intro with yours. I still need to know how the leak was fixed, though. The code change is here https://github.com/jbossas/jboss-eap/pull/721/files. The "how the leak was fixed" is that we no longer use an invalid query name when checking the query cache statistics. We found that passing an invalid query name, not only returned invalid results but it caused each invalid query name to be added to the Hibernate statistics. |