You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2004/03/29 15:48:42 UTC
DO NOT REPLY [Bug 28014] New: -
While uploading war file, running webapplication must not be stopped
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=28014>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28014
While uploading war file, running webapplication must not be stopped
Summary: While uploading war file, running webapplication must
not be stopped
Product: Tomcat 5
Version: 5.0.19
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Webapps:Manager
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: vspa@mail.ru
Hi, everybody.
There is a problem with manager (I use it via ant tasks from catalina-ant.jar).
I hoped, it would be solved in 5.x generation of tomcat, but apparently it's
not, so I decided to fill in this request.
Suppose I have a webapplication running on a production server and I want to
replace it with newer version. Ant "deploy" task (even with
attribute "update=true") does the following: first undeploy existing app, then
upload new war (depending on connection, in my case, it can take up to 2
minutes), then deploy it.
All that time, while war file was uploading, webapplication was inaccessible,
also, if uploading failed for some reasons, webapp is left in undeployed state.
So, my suggestion is to change behaviour of manager "deploy" functionality in
such a way, that war file first gets uploaded to the server, and only after
that the process of redeployment starts.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org