axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <>
Subject [jira] Commented: (AXIS2-4072) URLClassloader locking jarfiles on Windows
Date Mon, 13 Oct 2008 19:00:48 GMT


Jarek Gawor commented on AXIS2-4072:

Forgot to mention: thanks Tim for the patch!

> URLClassloader locking jarfiles on Windows 
> -------------------------------------------
>                 Key: AXIS2-4072
>                 URL:
>             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
>             Fix For: nightly
>         Attachments: 4072-2.patch, 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. 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:
For additional commands, e-mail:

View raw message