-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris,
On 11/14/12 11:02 AM, chris derham wrote: > My simple thought was that it sounds like your code isn't working. > You have more load than one tomcat instance can handle, which > overloads that instance. You are trying to write code to handle > this situation, and seem convinced that the only solution is to > alter tomcat such that you can detect/handle this occurrence in a > way that is easier for your software. I think this is an accurate summary of the proposal. Honestly, it does make *some* sense because the lb's job is to determine what is going on with the backend servers and distribute load. If one backend server is unhealthy, the lb needs to know about it. I'm not sure that pushing HTTP connections through to the backend is the proper way to do that - -- there *are* other ways to determine if Tomcat is under heavy load and those options do not necessarily use HTTP request/response to test them. For instance, if you use AJP, you can use cping/cpong. You can probably also use JMX (but that requires that the client has a JMX client available to it, or that you do something like use HTTP requests to the manager webapp's JMXProxyServlet). - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlCkB7UACgkQ9CaO5/Lv0PB1tACgvQ59BYQ+THOajPGRJSXVGawz OJkAoIgVD1hzfHoDxyz54wFmeF4tnNZU =2a7f -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
