servicemix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philippe Pinheiro (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SM-410) Component Uninstallation : ClassLoader not removed from JVM
Date Thu, 18 May 2006 06:51:51 GMT
    [ https://issues.apache.org/activemq/browse/SM-410?page=comments#action_36180 ] 

Philippe Pinheiro commented on SM-410:
--------------------------------------

Here is exactly what I have done with one example provided by servicemix 3.0 :

I downloaded the latest incubator servicemix 3.0 release (10-May-2006) 
and I just built the components and sa of the example : bpel-bpe as explained in the readme.txt

I started servicemix, I installed the 2 components, I deployed the su, I deleted the su, I
deleted the components
and in wdir/components the jars of the components are not deleted and they stay locked until
I stop servicemix.





> Component Uninstallation : ClassLoader not removed from JVM
> -----------------------------------------------------------
>
>          Key: SM-410
>          URL: https://issues.apache.org/activemq/browse/SM-410
>      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:
   https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message