axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Krystian Szczesny (JIRA)" <>
Subject [jira] Commented: (AXIS2-3552) Axis2 on Jetty & Tomcat bug: work dir is deleted on jetty shut down
Date Fri, 07 Mar 2008 10:13:46 GMT


Krystian Szczesny commented on AXIS2-3552:


this issue is not a web container issue but Axis2.
Jetty doesn't have ConfigurationContext.cleanupTemp() method, and it is doing nothing to the
The cause of problem is hidden somewhere within Axis2 source.

If you can, try using Axis2 1.2 - it works great. Unfortunately I can't because I depend on
features presented in 1.3.

> Axis2 on Jetty & Tomcat bug: work dir is deleted on jetty shut down
> -------------------------------------------------------------------
>                 Key: AXIS2-3552
>                 URL:
>             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,
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:
> 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:
For additional commands, e-mail:

View raw message