https://bz.apache.org/bugzilla/show_bug.cgi?id=64080
--- Comment #11 from Christopher Schultz <ch...@christopherschultz.net> --- (In reply to carbattles from comment #8) > If it is any help, our setup is 12 tomcat servers, with load balancer in > front. Our build process will restart the tomcat servers in sequence. We > expect that not a single request is dropped, however may process slower. If the expectation is that a request (from the client's perspective) will not be dropped, then I think you can solve this at the load-balancer with retry-based fail-over: the lb takes care of the fail-over and the client detects no problems at all. If you refuse to allow a request to an individual node to be dropped, that is a much taller order. In my environment, we tell the lb that the nodes are coming down so we avoid any of this. The lb allows all in-flight requests to complete and we only shut-down the node after that point. No new requests are sent to the target node after the lb is told to take it (softly) out of service. The only time requests should ever be dropped in this situation is if a node unexpectedly goes down. We do this using mod_jk with DISABLED and STOP states. mod_proxy_* has these same states and can be used with either AJP or HTTP as the communication protocol. I'm not sure if this gives you any viable alternatives, here, but I believe it allows you to accomplish your goal without adding a lot of complexity to the application server (i.e. Tomcat). -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
