Back to bug 1037636
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Scott Marlow | 2013-12-03 14:33:06 UTC | Component | JPA | |
| CC | smarlow | |||
| Jimmy Wilson | 2013-12-04 08:05:57 UTC | CC | jawilson | |
| Blocks | 1027004 | |||
| Scott Marlow | 2013-12-05 11:39:06 UTC | Target Release | --- | EAP 6.2.CP0a, EAP 6.3.0 |
| Component | jbossas, JPA | JPA | ||
| Assignee | fnasser | smarlow | ||
| QA Contact | zroubali | |||
| Fernando Nasser | 2013-12-05 15:48:16 UTC | CC | fnasser | |
| John Doyle | 2013-12-06 15:44:23 UTC | CC | jdoyle | |
| Carlo de Wolf | 2013-12-09 10:56:51 UTC | Target Release | EAP 6.3.0 | |
| CC | cdewolf | |||
| Scott Marlow | 2013-12-12 02:09:16 UTC | Blocks | 1040733 | |
| mark yarborough | 2013-12-16 13:08:41 UTC | Target Release | EAP 6.2.CP0a | EAP 6.2.1 |
| Carlo de Wolf | 2013-12-16 14:54:39 UTC | Blocks | 1040733 | |
| Depends On | 1040733 | |||
| Jimmy Wilson | 2013-12-16 14:56:45 UTC | Status | NEW | POST |
| mark yarborough | 2013-12-17 01:47:55 UTC | CC | myarboro | |
| Carlo de Wolf | 2014-01-08 15:04:27 UTC | Status | POST | MODIFIED |
| mark yarborough | 2014-01-13 13:51:27 UTC | Summary | Memory leak in JBoss AS / Hibernate JPA integration | [???] (6.2.x) Memory leak in JBoss AS / Hibernate JPA integration |
| mark yarborough | 2014-01-13 13:53:30 UTC | Summary | [???] (6.2.x) Memory leak in JBoss AS / Hibernate JPA integration | [GSS] (6.2.x) Memory leak in JBoss AS / Hibernate JPA integration |
| Carlo de Wolf | 2014-01-16 15:13:46 UTC | Target Milestone | --- | CR1 |
| Scott Mumford | 2014-01-20 05:58:46 UTC | CC | smumford | |
| Vaclav Tunka | 2014-01-20 22:17:53 UTC | Status | MODIFIED | ON_QA |
| Scott Mumford | 2014-01-23 03:30:33 UTC | Doc Text | A memory leak was found in the integration between JBoss EAP and the Hibernate JPA. When a persistence unit with 2nd level cache and statistics enabled was deployed, each query for "query-cache" elements produces new elements. Searches performed after this point could then query all elements. Depending on the number of queries and new elements this leak had the potential to kill the JVM within seven days. The leak was resolved by... | |
| Flags | needinfo?(smarlow) | |||
| Martin Simka | 2014-01-23 13:58:03 UTC | Status | ON_QA | VERIFIED |
| CC | msimka | |||
| Scott Marlow | 2014-01-23 15:55:50 UTC | Flags | needinfo?(smarlow) | |
| Scott Mumford | 2014-01-23 23:53:57 UTC | Doc Text | A memory leak was found in the integration between JBoss EAP and the Hibernate JPA. When a persistence unit with 2nd level cache and statistics enabled was deployed, each query for "query-cache" elements produces new elements. Searches performed after this point could then query all elements. Depending on the number of queries and new elements this leak had the potential to kill the JVM within seven days. The leak was resolved by... | 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)' |
| Flags | needinfo?(smarlow) | |||
| Scott Marlow | 2014-01-24 03:04:33 UTC | Flags | needinfo?(smarlow) | |
| Scott Mumford | 2014-01-28 00:07:57 UTC | 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)' | 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)' This release no longer uses an invalid query name when checking the query cache statistics. It was 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. |
| Lucas Costi | 2014-01-28 01:00:43 UTC | CC | lcosti | |
| 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)' This release no longer uses an invalid query name when checking the query cache statistics. It was 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. | 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. |
||
| mark yarborough | 2014-02-24 20:14:39 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2014-02-24 15:14:39 UTC | |||
| Russell Dickenson | 2017-10-10 00:16:45 UTC | Docs Contact | rdickens |
Back to bug 1037636