[GLASSFISH-18787] Classloader leak in com.sun.xml.ws.server.WSEndpointImpl Created: 06/Jun/12 Updated: 20/Dec/16 Resolved: 26/Jul/12
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
After undeploying a web app which uses JAX-WS web services LazyMOMProvider still references the WS implementation class. This causes all the classes loaded by the web app classloader to be referenced until the app server restart.
It seems that this if clause in WSEndpoinImpl.closeManagedObjectManager evaluates to true and thus prevents the unregistration:
// ManagedObjectManager doesn't need to be closed because it exists only as a proxy
|Comment by syvalta [ 06/Jun/12 ]|
The instance is always registered during creation in the constructor, so it should be unconditionally unregistered in the dispose. I guess the fix would be to move LazyMOMProvider.INSTANCE.unregisterEndpoint(this) out of the if blocks so that it is always executed.
|Comment by Lukas Jungmann [ 19/Jun/12 ]|
fixed in jaxws-ri workspace, will get to GF in the next integration
|Comment by Lukas Jungmann [ 26/Jul/12 ]|
integrated in svn r.55202