Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Apache webserver is talking to tomcat and putting him into error state, if he isn't reachable ("heartbeat") but also putting him into error state if the application has internal problems.

Problems like a database, which can't be accessable etc.

How does tomcat recognize this? How does the internal check of tomcat look like/work and what is he doing, to decide if the deployed application is OK or NOT OK and communicating this to the apache webserver, to put him out of load?


share|improve this question
"But also putting him into error state if the application has internal problems" Where did you read that? As you say, how would it know? How would anybody except the application know? I suggest you are misinformed. – EJP Jun 26 '12 at 1:46
this is no misinformation, but a personal sighting. Apache put an application server into error state, although application server was available and running, but the application itself stopped working... and the goal is to find this "How is apache Tomcat checking the application if OK/NOK" – TOM Jul 13 '12 at 10:54

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.