On Mon, Jan 17, 2005 at 11:52:14AM -0600, Stephen Charles Huey wrote: : working with our BigIP said that when he was running Apache on either of : the Linux servers, the load balancer could tell that the http service : was running, but when Tomcat was running, it didn't know what to check : for on a service level, so in the end, they had to set it up to just do : a TCP check to see if the port was open.
IIRC BigIP and other load balancers confirm a service (application) is available by periodically making a service-specific request and confirm the response. You're running a Tomcat webapp, hence such a "service-specific request" would be a URL call. The short version, then, would be to setup a resource -- it doesn't even have to be a full servlet or JSP, even a plain-text file containing "I'm Alive" will do -- and put it in a location accessible via URL. If the BigIP is able to fetch the document and it finds "I'm Alive" in it, it flags your application/service as alive and moves on. If you want to get fancy, make the resource a status page and have BigIP confirm it sees "OK" in the right spots. : He says this isn't ideal since the port being open doesn't mean the : service is up (meaning Tomcat). This is true: Tomcat can respond to TCP/IP connections on that port, but that doesn't mean your app is working as expected. : He thinks that Tomcat should start up : the http service (I guess he means httpd) when it starts--that maybe I : just need to look around in Tomcat's configuration for the place to set : this, but I'm not so sure that this is the case. This doesn't realy make sense... Are you using Tomcat on its own, or do you have Apache in front of it? In the former case, you've enabled the HTTP connector, and in turn what I described above should solve the problem. -QM -- software -- http://www.brandxdev.net tech news -- http://www.RoarNetworX.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
