DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25596>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25596 application briefly unavailable when using manager to reload Summary: application briefly unavailable when using manager to reload Product: Tomcat 5 Version: 5.0.16 Platform: Other OS/Version: All Status: NEW Severity: Normal Priority: Other Component: Webapps:Manager AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When reloading a web application in production. Tomcat reports that the application is unavailable for a brief period of time. the reason for reloading the application is the jsp pages are precompiled and the application reloadable property is set to false. So on every migration we are forced to reload the application which leads to the problem described above. When using reloadable propery in development this doesn't happen even after recompiling all class files. Some of the pages on the server are pretty complex pages that requires a lot of users input and when the application is unavailable all the user's work is simply lost and they have to start over again. there are no error messages in the log files and no complains, the application uses struts and the reloading is using the Ant tasks shipped with Tomcat. Please advice what is the best configuration, may be reloadable is not so bad after all. P.S. the application doesn't take this long to load we are talking about couple of seconds at the most. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]