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=5329>. 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=5329 NT Service exits startup before Tomcat is finished starting up. [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Unknown |Other Connectors ------- Additional Comments From [EMAIL PROTECTED] 2001-12-10 18:26 ------- Although more flexible connection handling in Apache might be desireable for some purposes, I do not believe that modifing the native code in Apache to only connect on demand would be a desireable solution to the problem. You would still run into problems for the short time that the connector is not yet ready to accept connections, and would also cause clients to recieve a 500 or 404 errors until the connector is ready to accept connections. Changing the code in Apache (and other native webservers) to accomodate an issue caused by an "inconsistency" in the Tomcat connectors would be undesireable if Tomcat is to remain independent of other software. I firmly believe that a piece of software (especially services on a server) should only "claim" to be ready if it is completly ready for all clients to access the service. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
