[
https://issues.apache.org/jira/browse/AXIS2-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Krystian Szczesny updated AXIS2-3552:
-------------------------------------
Description:
When shutting down Jetty version 6.1.2+ with Axis2 1.3+ warfile deployed, work
dir gets almost entirely deleted. The only thing that remains is WEB-INF/lib
directory [empty on HP-UX, full of libs on WinXP].
With Axis2 1.2- this problem does not occur. When deploying Axis2 1.2- on Jetty
version 6.1.2+ everything works just fine. When shutting down jetty work dir
remains as it was.
It is very easy to recreate this error: download jetty from
http://dist.codehaus.org/jetty/jetty-6.1.7/, unpack it, create 'work' directory
in jetty directory structure, put default axis2.war file in webapps dir and run
jetty. Everything should go just fine and Axis2 should work. Shut down jetty
and check the work dir. There will be nothing there accept WEB-INF/lib. Jetty
will not redeploy the application, what IMO means that it wasn't in fact jetty
deleting the directories.
I have also created an issue in Jetty's Jira:
http://jira.codehaus.org/browse/JETTY-514
Jetty ticket has been closed, as Jan Bartel proven this bug occurs on Tomcat as
well!!
was:
When shutting down Jetty version 6.1.2+ with Axis2 1.3+ warfile deployed, work
dir gets almost entirely deleted. The only thing that remains is WEB-INF/lib
directory [empty on HP-UX, full of libs on WinXP].
With Axis2 1.2- this problem does not occur. When deploying Axis2 1.2- on Jetty
version 6.1.2+ everything works just fine. When shutting down jetty work dir
remains as it was.
It is very easy to recreate this error: download jetty from
http://dist.codehaus.org/jetty/jetty-6.1.7/, unpack it, create 'work' directory
in jetty directory structure, put default axis2.war file in webapps dir and run
jetty. Everything should go just fine and Axis2 should work. Shut down jetty
and check the work dir. There will be nothing there accept WEB-INF/lib. Jetty
will not redeploy the application, what IMO means that it wasn't in fact jetty
deleting the directories.
I have also created an issue in Jetty's Jira:
http://jira.codehaus.org/browse/JETTY-514
Environment: HP-UX and Windows XP SP2, JAVA 1.5 (was: HP-UX and Windows XP
SP2)
Summary: Axis2 on Jetty & Tomcat bug: work dir is deleted on jetty shut
down (was: Axis2 on Jetty bug: work dir is deleted on jetty shut down)
This bug occurs on Tomcat as well!
> Axis2 on Jetty & Tomcat bug: work dir is deleted on jetty shut down
> -------------------------------------------------------------------
>
> Key: AXIS2-3552
> URL: https://issues.apache.org/jira/browse/AXIS2-3552
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.4, 1.3, nightly
> Environment: HP-UX and Windows XP SP2, JAVA 1.5
> Reporter: Krystian Szczesny
> Priority: Critical
> Fix For: 1.4
>
>
> When shutting down Jetty version 6.1.2+ with Axis2 1.3+ warfile deployed,
> work dir gets almost entirely deleted. The only thing that remains is
> WEB-INF/lib directory [empty on HP-UX, full of libs on WinXP].
> With Axis2 1.2- this problem does not occur. When deploying Axis2 1.2- on
> Jetty version 6.1.2+ everything works just fine. When shutting down jetty
> work dir remains as it was.
> It is very easy to recreate this error: download jetty from
> http://dist.codehaus.org/jetty/jetty-6.1.7/, unpack it, create 'work'
> directory in jetty directory structure, put default axis2.war file in webapps
> dir and run jetty. Everything should go just fine and Axis2 should work. Shut
> down jetty and check the work dir. There will be nothing there accept
> WEB-INF/lib. Jetty will not redeploy the application, what IMO means that it
> wasn't in fact jetty deleting the directories.
> I have also created an issue in Jetty's Jira:
> http://jira.codehaus.org/browse/JETTY-514
> Jetty ticket has been closed, as Jan Bartel proven this bug occurs on Tomcat
> as well!!
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
