[ https://issues.apache.org/activemq/browse/SM-410?page=all ]
Guillaume Nodet resolved SM-410.
--------------------------------
Fix Version/s: 3.1
Resolution: Fixed
Assignee: Guillaume Nodet
URL: http://svn.apache.org/viewvc?view=rev&rev=486638
URL: http://svn.apache.org/viewvc?view=rev&rev=486639
URL: http://svn.apache.org/viewvc?view=rev&rev=486666
URL: http://svn.apache.org/viewvc?view=rev&rev=486673
> 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-core
> Affects Versions: 3.0-M1
> Reporter: Philippe Pinheiro
> Assigned To: Guillaume Nodet
> Fix For: 3.1
>
> 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
