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 "Kent Tong (JIRA)" <ji...@apache.org> on 2006/07/30 13:57:14 UTC
[jira] Commented: (AXIS2-673) aar file is locked in Tomcat
[ http://issues.apache.org/jira/browse/AXIS2-673?page=comments#action_12424383 ]
Kent Tong commented on AXIS2-673:
---------------------------------
I just tried it using the nightly build on June 16 and the problem still persists. The .aar file is locked even for services that had been there when Tomcat was started.
> aar file is locked in Tomcat
> ----------------------------
>
> Key: AXIS2-673
> URL: http://issues.apache.org/jira/browse/AXIS2-673
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: deployment
> Affects Versions: 1.0
> Environment: Axis2 1.0 RC4. Tomcat 5.5.7. Win XP.
> Reporter: Kent Tong
> Assigned To: Deepal Jayasinghe
>
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org