[jboss-jira] [JBoss JIRA] Resolved: (JBCL-119) DependencyInfo.removeDependsOnMe never called

[Thomas Diesler (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBCL-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Diesler resolved JBCL-119.
---------------------------------

    Resolution: Done


I added this to 

Module.removeIDependOn

      // Remove the DependsOnMe part of this item
      Object iDependOn = item.getIDependOn();
      if (iDependOn != null)
      {
         Module otherModule = domain.getModule(iDependOn.toString());
         DependencyInfo otherDependencyInfo = otherModule.getControllerContext().getDependencyInfo();
         otherDependencyInfo.removeDependsOnMe(item);
      }


> DependencyInfo.removeDependsOnMe never called
> ---------------------------------------------
>
>                 Key: JBCL-119
>                 URL: https://jira.jboss.org/jira/browse/JBCL-119
>             Project: JBoss ClassLoader
>          Issue Type: Bug
>          Components: Dependencies
>            Reporter: Thomas Diesler
>            Assignee: Thomas Diesler
>             Fix For: JBossCL.2.0.7.GA
>
>
> Consider this
> BundleA
>   exports A
> BundleB
>   imports A
> #1 install BundleA
> #2 install/start BundleB
> #3 uninstall BundleB
> The DependencyInfo of BundleA holds a dependsOnMe entry for BundleB that is never removed.
> This contributes to the memory leak that we see in [JBOSGI-155]

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira