[
https://issues.jboss.org/browse/WFLY-9849?page=com.atlassian.jira.plugin....
]
Scott Marlow edited comment on WFLY-9849 at 6/1/18 10:45 AM:
-------------------------------------------------------------
Updated: I don't seem to actually see a leak with Hibernate ORM 5.1.14.Final, as there
weren't any strong references to the (undeployed)
org.hibernate.internal.SessionFactoryImpl objects
was (Author: smarlow):
I do seem to see a leak also with Hibernate ORM 5.1.14.Final but not 5.3.1.Final. Could
you verify that you don't see a leak with WildFly 13 started up via
"standalone.sh -Dee8.preview.mode=true".
Hibernate session related leak on module undeployment
-----------------------------------------------------
Key: WFLY-9849
URL:
https://issues.jboss.org/browse/WFLY-9849
Project: WildFly
Issue Type: Bug
Affects Versions: 11.0.0.Final, 12.0.0.Final
Environment: * Ubuntu 16.04.3 LTS
* OpenJDK 1.8.0_151
* Wildfly 11.0.0.Final
Seems to occur at least on CentOS 7/OpenJDK 1.8.0_151 also.
Reporter: Joni Syri
Assignee: Scott Marlow
In some cases it seems that removing deployment from the Wildfly, doesn't free up
{{org.hibernate.internal.SessionFactoryImpl}}- instance related to the deployment. (plus
some other Hibernate related classes). This can be seen by taking memory dump with
VisualVM and looking up {{SessionFactoryImpl}} instances.
This leads to cumulative memory leak in cases, where application is repeatedly
deployed/undeployed (or updated).
updated: Seems to occur on 12.0.0.Final also
Memory dumps can be found at
https://drive.google.com/drive/folders/1WbHB6hRpr_lrc4yb4yxWLpeObmJlNCzD (wildfly-leak-1
is after first deployment, wildfly-leak-2 after few re-deploys)
server.log
https://drive.google.com/file/d/1I32OTnPWeopVEtRC3ol-pjkH2dlkLizD/view?us...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)