Closed glassfishrobot closed 11 years ago
@glassfishrobot Commented shreedhar_ganapathy said: -> Deployment -> Hong for further eval.
@glassfishrobot Commented @honghzzhang said: Assigning to the webservices team to follow up on this to see we can apply the patch in the webservices code to properly clean up endpoints for undeployment.
@glassfishrobot Commented @lukasj said: http://java.net/projects/glassfish/sources/svn/revision/59263
@glassfishrobot Commented This issue was imported from java.net JIRA GLASSFISH-19096
@glassfishrobot Commented Reported by bebbo
@glassfishrobot Commented Marked as fixed on Thursday, February 7th 2013, 6:26:33 am
package com.sun.xml.ws.api.server;
Memory leak after undeployment of an ear.
deploy an ear with web services and jpa invoke at least one ws which uses jpa deploy the same ear again
=> the first deployed ear is not properly undeployed. (VisualVM is showing two instances of EarClassLoader
It's caused by unreleased but already disposed endpoints.
my patch performs some cleanup when registering an endpoint. I bet there is a proper solution, but this works.
Affected Versions
[3.1.2]