servicemix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philippe Pinheiro (JIRA)" <>
Subject [jira] Commented: (SM-410) Component Uninstallation : ClassLoader not removed from JVM
Date Fri, 12 May 2006 07:16:30 GMT
    [ ] 

Philippe Pinheiro commented on SM-410:

I have exactly the same problem on a XP SP2 with jdk1.5.0_06.

> Component Uninstallation : ClassLoader not removed from JVM
> -----------------------------------------------------------
>          Key: SM-410
>          URL:
>      Project: ServiceMix
>         Type: Bug

>   Components: servicemix-components
>     Versions: 3.0-M1
>     Reporter: Philippe Pinheiro

> 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:
For more information on JIRA, see:

View raw message