[ https://issues.apache.org/activemq/browse/SM-410?page=comments#action_37205 ] Philippe Pinheiro commented on SM-410: --------------------------------------
I confirm that this problem still exist on the version 3.0 I also want to add that the number of classloader (org.apache.xbean.classloader.JarFileClassLoader) increases in the JVM after install / uninstall of the same component meaning that this issue is the cause of a memory leak. > Component Uninstallation : ClassLoader not removed from JVM > ----------------------------------------------------------- > > Key: SM-410 > URL: https://issues.apache.org/activemq/browse/SM-410 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-components > Affects Versions: 3.0-M1 > Reporter: Philippe Pinheiro > Attachments: servicemix.log > > > After component uninstallation, the corresponding component classloader is > not removed from the JVM and the jars in the wdir are locked. > To reproduce this bug you just need to : > - install the component : servicemix-jms by putting the jar on the install > folder > - install a service assembly containing a service unit with some endpoints : > copy the zip in the deploy folder > - uninstall the service assembly : delete the zip file > - uninstall the component : delete the jar file > Then you will see that some files are still locked on the wdir folder. > Furthermore I use JSwat to remotely debug the JVM, with this tool you can see > that the ParentFirstClassloader of > the servicemix-jms component is still loaded. > I also found that if a service assembly is not installed then this bug > doesn't occur. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
