Well 504 seems more correct in our case
2005/4/19, William A. Rowe, Jr. [EMAIL PROTECTED]:
At 02:04 PM 4/18/2005, Mladen Turk wrote:
This is bug, and will be fixed.
It should return SERVER_BUSY (503) if can not connect to Tomcat.
You can try to use the load balancer with the single worker,
Using the same configuration files for 1.2.8 and 1.2.10, I get differing
behaviors when Tomcat isn't running.
Machine:
Solaris 8, Apache 1.3.33
Relevant configuration
JkMount /*.jsp ajp13
1.2.8 Response:
!DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN
HTMLHEAD
TITLE500 Internal Server
Marx, Mitchell E (Mitch), ALABS wrote:
Using the same configuration files for 1.2.8 and 1.2.10, I get differing
behaviors when Tomcat isn't running.
1.2.10 Response:
!DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN
HTMLHEAD
TITLE200 OK/TITLE
This is bug, and will be fixed.
It should return
At 02:04 PM 4/18/2005, Mladen Turk wrote:
This is bug, and will be fixed.
It should return SERVER_BUSY (503) if can not connect to Tomcat.
You can try to use the load balancer with the single worker, and
it should work like explained.
It depends;
Connection refused ==
503
