You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Philippe Pinheiro (JIRA)" <ji...@apache.org> on 2006/04/26 15:09:47 UTC
[jira] Created: (SM-410) Component Uninstallation : ClassLoader not
removed from JVM
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
[jira] Commented: (SM-410) Component Uninstallation : ClassLoader
not removed from JVM
Posted by "Philippe Pinheiro (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-410?page=comments#action_36123 ]
Philippe Pinheiro commented on SM-410:
--------------------------------------
I use jdk1.5.0_06 / W2k SP4.
I have the same behavior on 3 different PCs with this configuration.
> 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
[jira] Commented: (SM-410) Component Uninstallation : ClassLoader
not removed from JVM
Posted by "Nicolas Biri (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-410?page=comments#action_36886 ]
Nicolas Biri commented on SM-410:
---------------------------------
Same problem on win nt + jdk5.0.7 : loan broker and soap binding uninstall is unable to remove component directories
> 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
>
> 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
[jira] Updated: (SM-410) Component Uninstallation : ClassLoader not
removed from JVM
Posted by "Aleksei K. Prokopchook (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-410?page=all ]
Aleksei K. Prokopchook updated SM-410:
--------------------------------------
Attachment: servicemix.log
I have similar problems: ServiceMix (or lwcontainer component) seems to be not cleaning working directory if installation/deployment zip file contains jars in it.
Java Version: 1.5.0_07
OS Version: Microsoft Windows XP Professional Version 2002 Service Pack 2.
Here's the simple way to reproduce the problem:
Download ServiceMix Release 3.0 (http://servicemix.org/site/servicemix-30.html, binary version for Windows);
Unzip archive, and then run "bin/servicemix" from the command line;
Copy servicemix-shared-3.0-incubating-installer.zip from components directory to install directory;
Copy servicemix-lwcontainer-3.0-incubating-installer.zip from components directory to install directory;
Wait couple seconds until it's installed;
Delete servicemix-lwcontainer-3.0-incubating-installer.zip from install directory.
Everything is removed from the working directory except
<Service Mix Directory>\data\smx\components\servicemix-lwcontainer\version_1\lib\servicemix-lwcontainer-3.0-incubating.jar.
I'm attaching the complete log file for the above actions (notice WARN-level message before the last message!)
Same thing happens when you delete zip files from deploy directory (service assemblies deployed via lwcontainer component) - if they contains jar files, they aren't deleted after un-deploying service assembly.
> 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
[jira] Updated: (SM-410) Component Uninstallation : ClassLoader not
removed from JVM
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-410?page=all ]
Guillaume Nodet updated SM-410:
-------------------------------
Component/s: servicemix-core
(was: servicemix-components)
> 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
> 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
[jira] Commented: (SM-410) Component Uninstallation : ClassLoader
not removed from JVM
Posted by "Philippe Pinheiro (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-410?page=comments#action_36161 ]
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: 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
[jira] Commented: (SM-410) Component Uninstallation : ClassLoader
not removed from JVM
Posted by "Philippe Pinheiro (JIRA)" <ji...@apache.org>.
[ 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
[jira] Resolved: (SM-410) Component Uninstallation : ClassLoader
not removed from JVM
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (SM-410) Component Uninstallation : ClassLoader
not removed from JVM
Posted by "Philippe Pinheiro (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (SM-410) Component Uninstallation : ClassLoader
not removed from JVM
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-410?page=comments#action_36162 ]
Guillaume Nodet commented on SM-410:
------------------------------------
Could you please attach the SA you use to test and the servicemix.xml configuration file used.
Also, do you use the ServiceMix distribution, have you done any modifications to it (add jar, etc..) ?
> 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
[jira] Commented: (SM-410) Component Uninstallation : ClassLoader
not removed from JVM
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-410?page=comments#action_36100 ]
Guillaume Nodet commented on SM-410:
------------------------------------
I have tried to reproduce the error (on latest svn head) without any sucsess.
I ' m using a modified version of the soap-binding example to include an http binding and a jms binding.
When I undeploy the SA, then uninstall the components, all directories are removed.
This may be a problem dependant of the JMS / OS.
I use JDK 5 / XP.
> 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