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=20907>. 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=20907 user is left with no message if an error occurs early during startup Summary: user is left with no message if an error occurs early during startup Product: Tomcat 4 Version: 4.1.24 Platform: PC OS/Version: Windows XP Status: NEW Severity: Enhancement Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When an error occurs early during startup of Tomcat, nothing is written to the logfiles (presumably because the loggers are not initialized at this point). To make the situation worse, the window containing Tomcat closes before the user has got any chance to read the messages. This also happens if Tomcat was started from the command prompt. My proposals are the following: 1. Don't open Tomcat in an own window if it was started from the command prompt. Why don't we direct stdio to the command prompt that started Tomcat? 2. In the case that Tomcat needs its own window, why not let the user decide when to close it? At least a 5 second delay would be appropriate. Regards, Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
