Hi -

Running a Single Apache Web Server (1.3.36) to 2 Tomcat App Servers
(5.5.17) via mod_jk (1.2.19) on Unix Solaris.  Apache Tomcat Connector
setup for loadbalance which it does just fine.  Issue is that when 1
Tomcat goes into error state the cluster becomes unavailable.  Apache
sees the 1 Tomcat in error state but does not seem to be able to
ignore it and send traffic to the healthy tomcat.  Enclosed is log
entry from mod_jk showing that Apache knows about the error state.  I
see lots of these:

[Fri Oct 03 18:40:02 2008] [24045:0001] [error]
ajp_service::jk_ajp_common.c (1879): (cbap1) Connecting to tomcat
failed. Tomcat is probably not started or is listening on the wrong
port
[Fri Oct 03 18:40:02 2008] [24045:0001] [info]
service::jk_lb_worker.c (906): service failed, worker cbap1 is in
error state
[Fri Oct 03 18:42:17 2008] [20789:0001] [info]
jk_open_socket::jk_connect.c (450): connect to IP REMOVED failed with
errno=145
[Fri Oct 03 18:42:17 2008] [20789:0001] [info]
ajp_connect_to_endpoint::jk_ajp_common.c (872): Failed opening socket
to (IP REMOVED) with (errno=145)
[Fri Oct 03 18:42:17 2008] [20789:0001] [info]
ajp_send_request::jk_ajp_common.c (1247): (cbap1) error connecting to
the backend server (errno=145)
[Fri Oct 03 18:42:17 2008] [20789:0001] [info]
ajp_service::jk_ajp_common.c (1867): (cbap1) sending request to tomcat
failed,  recoverable operation attempt=2
[Fri Oct 03 18:42:17 2008] [20789:0001] [error]
ajp_service::jk_ajp_common.c (1879): (cbap1) Connecting to tomcat
failed. Tomcat is probably not started or is listening on the wrong
port
[Fri Oct 03 18:42:17 2008] [20789:0001] [info]
service::jk_lb_worker.c (906): service failed, worker cbap1 is in
error state
[Fri Oct 03 18:42:47 2008] [24046:0001] [info]
jk_open_socket::jk_connect.c (450): connect to IP REMOVED failed with
errno=145
[Fri Oct 03 18:42:47 2008] [24046:0001] [info]
ajp_connect_to_endpoint::jk_ajp_common.c (872): Failed opening socket
to (IP REMOVED) with (errno=145)
[Fri Oct 03 18:42:47 2008] [24046:0001] [info]
ajp_send_request::jk_ajp_common.c (1247): (cbap1) error connecting to
the backend server (errno=145)
[Fri Oct 03 18:42:47 2008] [24046:0001] [info]
ajp_service::jk_ajp_common.c (1867): (cbap1) sending request to tomcat
failed,  recoverable operation attempt=2
[Fri Oct 03 18:42:47 2008] [24046:0001] [error]
ajp_service::jk_ajp_common.c (1879): (cbap1) Connecting to tomcat
failed. Tomcat is probably not started or is listening on the wrong
port
[Fri Oct 03 18:42:47 2008] [24046:0001] [info]
service::jk_lb_worker.c (906): service failed, worker cbap1 is in
error state
[Fri Oct 03 18:45:36 2008] [21777:0001] [info]
jk_open_socket::jk_connect.c (450): connect to IP REMOVED failed with
errno=145
[Fri Oct 03 18:45:36 2008] [21777:0001] [info]
ajp_connect_to_endpoint::jk_ajp_common.c (872): Failed opening socket
to (IP REMOVED) with (errno=145)
[Fri Oct 03 18:45:36 2008] [21777:0001] [info]
ajp_send_request::jk_ajp_common.c (1247): (cbap1) error connecting to
the backend server (errno=145)

If we shutdown the cbap1 which is in error then Apache is able to
serve pages again using the other Tomcat app server.  Note that cbap1
was in bad state and needed to be killed as it would not shutdown
normally.  (We are investigating as separate issue, but would like to
pursue this issue as to make cluster more resilient.)

My workers.properties is configured with a bare minimum of options.

worker.list=loadbalancer
worker.loadbalancer.type=lb
worker.loadbalancer.balance_workers=cbap1,cbap2
worker.loadbalancer.sticky_session=1
worker.cbap1.port=8690
worker.cbap1.host= edited for privacy
worker.cbap1.type=ajp13
worker.cbap1.lbfactor=10
worker.cbap1.socket_keepalive=1
# worker.cbap1.cachesize=5


worker.cbap2.port=8690
worker.cbap2.host=edited for privacy
worker.cbap2.type=ajp13
worker.cbap2.lbfactor=10
worker.cbap2.socket_keepalive=1
# worker.cbap2.cachesize=5



I am looking for suggestion as to other configuration properties which
should be added to help with error handling of the worker in error
state.  Or other points to review welcome.
THANK YOU for any help here.

Rgds,
Hunter.

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to