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 "Michael Heemskerk (JIRA)" <ji...@apache.org> on 2008/10/23 08:54:44 UTC
[jira] Created: (AXIS2-4094) CLONE -jars, mars and aars are locked
in the file system even after undeployment of the axis2 webapp
CLONE -jars, mars and aars are locked in the file system even after undeployment of the axis2 webapp
----------------------------------------------------------------------------------------------------
Key: AXIS2-4094
URL: https://issues.apache.org/jira/browse/AXIS2-4094
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: deployment
Affects Versions: 1.1
Environment: WinXP, Tomcat 4.1, Tomcat 5.5, WebSphere 6.0
Reporter: Michael Heemskerk
Assignee: Deepal Jayasinghe
Webapp containing axis2 servlet cannot be succesfuly undeployed because some of the files (jar, mar, aar) are locked and cannot be deleted until the servlet container is stopped.
--
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
[jira] Commented: (AXIS2-4094) CLONE -jars, mars and aars are
locked in the file system even after undeployment of the axis2 webapp
Posted by "Michael Heemskerk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642083#action_12642083 ]
Michael Heemskerk commented on AXIS2-4094:
------------------------------------------
The AXIS2-1916 bug has been marked as Resolved, but still appears is release 1.4.
Description copied from original bug report:
----------------------------
Here are the exact steps that indicate the bug:
1. start tomcat
2. deploy the axis2 war (using http://localhost:8080/manager/html, not hot deployment)
3. axis2 web app is listed among other applications on the same page (http://localhost:8080/manager/html) and axis2 folder appears in the tomcat's webapps folder
4. remove the webapp (using http://localhost:8080/manager/html again)
5. axis2 webapp is not listed among other applications, but the axis2 folder remains with the WEB-INF/lib and WEB-INF/modules subfolders and jars and mars locked in them; they cannot be deleted until tomcat is stopped
6. if autodeployment on tomcat is on, the axis2 webapp is listed as deployed again (after a few seconds), but cannot be used (only jars and mars survived)
- axis2 war that is deployed is the one built by ant script in webapp subfolder of axis2-1.4 dist (with or without the above change in axis2.xml)
- note that no service is invoked during this process, simply deploy + undeploy and it doesn't work
----------------------------
I'm have the same issue in release 1.4, on Glassfish v2ur2, Tomcat 6.0 and WebSphere 6.1 (all on WindowsXP/Windows 2003). Has the issue been reintroduced?
However, in version 1.4 only the jar files in WEB-INF/lib are locked. The mar en aar files can be successfully deleted when the webapp is removed.
A workaround is to create an EAR and move all the jars to WEB-INF/lib in the EAR and add the jars to the manifest file of the web project, but this should definitely be fixed (again?).
> CLONE -jars, mars and aars are locked in the file system even after undeployment of the axis2 webapp
> ----------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4094
> URL: https://issues.apache.org/jira/browse/AXIS2-4094
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: deployment
> Affects Versions: 1.1
> Environment: WinXP, Tomcat 4.1, Tomcat 5.5, WebSphere 6.0
> Reporter: Michael Heemskerk
> Assignee: Deepal Jayasinghe
>
> Webapp containing axis2 servlet cannot be succesfuly undeployed because some of the files (jar, mar, aar) are locked and cannot be deleted until the servlet container is stopped.
--
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
[jira] Updated: (AXIS2-4094) Jars are locked in the file system
even after undeployment of the axis2 webapp
Posted by "Michael Heemskerk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Heemskerk updated AXIS2-4094:
-------------------------------------
Description:
Webapp containing axis2 servlet cannot be succesfuly undeployed because jar files in WEB-INF/lib are locked and cannot be deleted until the servlet container is stopped.
was:Webapp containing axis2 servlet cannot be succesfuly undeployed because some of the files (jar, mar, aar) are locked and cannot be deleted until the servlet container is stopped.
Environment: WinXP, Tomcat 4.1, Tomcat 5.5, Tomcat 6, WebSphere 6.0 & 6.1, Glassfish 2, (was: WinXP, Tomcat 4.1, Tomcat 5.5, WebSphere 6.0)
Affects Version/s: (was: 1.1)
1.4.1
1.4
Summary: Jars are locked in the file system even after undeployment of the axis2 webapp (was: CLONE -jars, mars and aars are locked in the file system even after undeployment of the axis2 webapp)
> Jars are locked in the file system even after undeployment of the axis2 webapp
> ------------------------------------------------------------------------------
>
> Key: AXIS2-4094
> URL: https://issues.apache.org/jira/browse/AXIS2-4094
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: deployment
> Affects Versions: 1.4.1, 1.4
> Environment: WinXP, Tomcat 4.1, Tomcat 5.5, Tomcat 6, WebSphere 6.0 & 6.1, Glassfish 2,
> Reporter: Michael Heemskerk
> Assignee: Deepal Jayasinghe
>
> Webapp containing axis2 servlet cannot be succesfuly undeployed because jar files in WEB-INF/lib are locked and cannot be deleted until the servlet container is stopped.
--
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
[jira] Issue Comment Edited: (AXIS2-4094) CLONE -jars, mars and
aars are locked in the file system even after undeployment of the axis2
webapp
Posted by "Michael Heemskerk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642083#action_12642083 ]
michaelheemskerk edited comment on AXIS2-4094 at 10/23/08 12:00 AM:
---------------------------------------------------------------------
The AXIS2-1916 bug has been marked as Resolved, but still appears in release 1.4.
Description copied from original bug report:
----------------------------
Here are the exact steps that indicate the bug:
1. start tomcat
2. deploy the axis2 war (using http://localhost:8080/manager/html, not hot deployment)
3. axis2 web app is listed among other applications on the same page (http://localhost:8080/manager/html) and axis2 folder appears in the tomcat's webapps folder
4. remove the webapp (using http://localhost:8080/manager/html again)
5. axis2 webapp is not listed among other applications, but the axis2 folder remains with the WEB-INF/lib and WEB-INF/modules subfolders and jars and mars locked in them; they cannot be deleted until tomcat is stopped
6. if autodeployment on tomcat is on, the axis2 webapp is listed as deployed again (after a few seconds), but cannot be used (only jars and mars survived)
- axis2 war that is deployed is the one built by ant script in webapp subfolder of axis2-1.4 dist (with or without the above change in axis2.xml)
- note that no service is invoked during this process, simply deploy + undeploy and it doesn't work
----------------------------
I'm have the same issue in release 1.4, on Glassfish v2ur2, Tomcat 6.0 and WebSphere 6.1 (all on WindowsXP/Windows 2003). Has the issue been reintroduced?
However, in version 1.4 only the jar files in WEB-INF/lib are locked. The mar en aar files can be successfully deleted when the webapp is removed.
A workaround is to create an EAR and move all the jars to WEB-INF/lib in the EAR and add the jars to the manifest file of the web project, but this should definitely be fixed (again?).
was (Author: michaelheemskerk):
The AXIS2-1916 bug has been marked as Resolved, but still appears is release 1.4.
Description copied from original bug report:
----------------------------
Here are the exact steps that indicate the bug:
1. start tomcat
2. deploy the axis2 war (using http://localhost:8080/manager/html, not hot deployment)
3. axis2 web app is listed among other applications on the same page (http://localhost:8080/manager/html) and axis2 folder appears in the tomcat's webapps folder
4. remove the webapp (using http://localhost:8080/manager/html again)
5. axis2 webapp is not listed among other applications, but the axis2 folder remains with the WEB-INF/lib and WEB-INF/modules subfolders and jars and mars locked in them; they cannot be deleted until tomcat is stopped
6. if autodeployment on tomcat is on, the axis2 webapp is listed as deployed again (after a few seconds), but cannot be used (only jars and mars survived)
- axis2 war that is deployed is the one built by ant script in webapp subfolder of axis2-1.4 dist (with or without the above change in axis2.xml)
- note that no service is invoked during this process, simply deploy + undeploy and it doesn't work
----------------------------
I'm have the same issue in release 1.4, on Glassfish v2ur2, Tomcat 6.0 and WebSphere 6.1 (all on WindowsXP/Windows 2003). Has the issue been reintroduced?
However, in version 1.4 only the jar files in WEB-INF/lib are locked. The mar en aar files can be successfully deleted when the webapp is removed.
A workaround is to create an EAR and move all the jars to WEB-INF/lib in the EAR and add the jars to the manifest file of the web project, but this should definitely be fixed (again?).
> CLONE -jars, mars and aars are locked in the file system even after undeployment of the axis2 webapp
> ----------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4094
> URL: https://issues.apache.org/jira/browse/AXIS2-4094
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: deployment
> Affects Versions: 1.1
> Environment: WinXP, Tomcat 4.1, Tomcat 5.5, WebSphere 6.0
> Reporter: Michael Heemskerk
> Assignee: Deepal Jayasinghe
>
> Webapp containing axis2 servlet cannot be succesfuly undeployed because some of the files (jar, mar, aar) are locked and cannot be deleted until the servlet container is stopped.
--
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