[
http://issues.apache.org/jira/browse/AXIS2-673?page=comments#action_12378180 ]
Kent Tong commented on AXIS2-673:
---------------------------------
If it works in Linux, then this issue only exists in Windows. I tried using a
DOS shell or Windows Explorer and had the same result ("file in use"). Using
Cygwin the commands doesn't print any message but the file is still listed by
ls. In the case of Cygwin, after shutting tomcat, the file will be gone. I
guess this has something to do with the Posix subsystem in Windows.
But anyway, the point is that the aar file can't be deleted in Windows.
> aar file is locked in Tomcat
> ----------------------------
>
> Key: AXIS2-673
> URL: http://issues.apache.org/jira/browse/AXIS2-673
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: deployment
> Versions: 1.0
> Environment: Axis2 1.0 RC4. Tomcat 5.5.7. Win XP.
> Reporter: Kent Tong
>
> 1) Start Tomcat.
> 2) Put an aar file such as test.aar into webapps/Axis2/WEB-INF/services to
> hot-deploy it.
> 3) Try to delete the aar file. It says something to the effect of "file is
> being used by another process and can't be deleted".
> It means one can never hot-undeploy a service by deleting the aar file. This
> issue should have nothing to do with antiJARLocking as Axis2 is using a
> ZipInputStream to access the aar file. In fact, I've even tried setting
> antiJARLocking to true but the problem persists.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
