[
http://jira.jboss.com/jira/browse/JBAS-3696?page=comments#action_12343996 ]
Clebert Suconic commented on JBAS-3696:
---------------------------------------
my suggestion for a fix would be to modify destory on ServiceEndpointDeployer:
public void destroy(UnifiedDeploymentInfo udi) throws Throwable
{
log.debug("destroy: " + udi.url);
UnifiedMetaData wsMetaData = getUnifiedMetaData(udi);
if (wsMetaData != null)
{
// Destroy the service endpoints
for (ServiceMetaData serviceMetaData : wsMetaData.getServices())
{
for (EndpointMetaData epMetaData : serviceMetaData.getEndpoints())
{
ObjectName sepID =
((ServerEndpointMetaData)epMetaData).getServiceEndpointID();
epManager.destroyServiceEndpoint(sepID);
}
}
}
removeUnifiedMetaData(udi);
}
public void removeUnifiedMetaData(UnifiedDeploymentInfo udi)
{
metaDataMap.remove(udi.url.toExternalForm());
}
WebServices leaking redeployment
--------------------------------
Key: JBAS-3696
URL:
http://jira.jboss.com/jira/browse/JBAS-3696
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Clebert Suconic
Assigned To: Thomas Diesler
Priority: Blocker
Fix For: JBossAS-4.0.5.GA
org.jboss.ws.metadata.UnifiedMetaData has lots of strong references to ClassLoader, and
Undeployers are not releasing references to the metadata.
The current failures we are having on the TestSuite (OOME) are related to this task.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira