You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Davanum Srinivas (JIRA)" <ji...@apache.org> on 2008/10/08 01:24:44 UTC
[jira] Assigned: (AXIS2-4072) URLClassloader locking jarfiles on
Windows
[ https://issues.apache.org/jira/browse/AXIS2-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas reassigned AXIS2-4072:
---------------------------------------
Assignee: Jarek Gawor
Jarek,
Can you please take care of this?
thanks,
dims
> URLClassloader locking jarfiles on Windows
> -------------------------------------------
>
> Key: AXIS2-4072
> URL: https://issues.apache.org/jira/browse/AXIS2-4072
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.4.1
> Environment: Windows XP, Geronimo 2.1.3
> Reporter: Tim McConnell
> Assignee: Jarek Gawor
> Attachments: AXIS2-4072.patch
>
>
> There is at least one scenario using Axis2 and Geronimo that is causing jarfiles to get locked on Windows such that a deployed WAR cannot be either redeployed or uninstalled. Here is a brief description of the failing scenario:
> 1. A WAR file containing various jarfiles in the /lib directory is deployed on Geronimo 2.1.3
> 2. Navigate to the deployed app's address to generate the WSDL for the web service
> 3. Redeploy or uninstall of the WAR will now fail since all the jarfiles in the WAR /lib directory are locked by Windows and cannot be deleted.
> What appears to be happening is that there are three Axis2 URLClassLoaders in this scenario and at least two of them are creating their own ClassPath and URLClassPath$JarLoader objects that apparently are locking the jarfiles in the /lib directory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org