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 2006/02/16 13:09:30 UTC
DO NOT REPLY [Bug 38677] New: - Handle partially transferred war files more gracefully
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=38677>.
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=38677
Summary: Handle partially transferred war files more gracefully
Product: Tomcat 5
Version: 5.5.12
Platform: Other
OS/Version: other
Status: NEW
Severity: enhancement
Priority: P2
Component: Unknown
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: jain@gmx.net
During development I frequently redeploy war files by copying them to the
webapps directory and waiting for Tomcat to pick them up automatically. But it
frequently happens that Tomcat happens to check for war files while the file is
still being transferred, which results in an "Invalid or unreadable WAR file"
exception. Would it make sense to instead wait a few seconds (perhaps check if
the file size has changed), and retry?
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
DO NOT REPLY [Bug 38677] - Handle partially transferred war files more gracefully
Posted by bu...@apache.org.
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=38677>.
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=38677
yoavs@computer.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WORKSFORME
------- Additional Comments From yoavs@computer.org 2006-12-24 18:21 -------
I see your point. I guess if you want to stick with your use case, you should
set backgroundProcessorDelay on your Host to something greater than the time it
takes to copy your new WAR: see
http://tomcat.apache.org/tomcat-5.5-doc/config/host.html for more.
However, what I usually do is more deterministic since I hate waiting on these
timings, so I would recommend it over your approach anyways: use the Manager
webapp to (re)deploy or (re)start your apps. Let's say your app lives at
context path /foo and your new WAR is created at /usr/local/bar.war. Simply
bookmark the appropriate URL as explained in
http://tomcat.apache.org/tomcat-5.5-doc/manager-howto.html#Deploy%20A%20New%20Application%20from%20a%20Local%20Path
and ping it when you want to redeploy. That seems to work well for me...
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org