[ 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
