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 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
