https://issues.apache.org/bugzilla/show_bug.cgi?id=50534
Summary: recover_time doesn't work with network issues
Product: Tomcat Connectors
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: mod_jk
AssignedTo: [email protected]
ReportedBy: [email protected]
Hi,
I defined a loadbalancer with 2 workers (who connect to JBoss application
server)
When I stopped both Jboss backends, I got immediately a 503 response from the
loadbalancer, this is ok.
But when you're having network issues, for example broker firewall,switch
the workers goes in error (normal), but when they are both in error, I don't
receive immedately a 503 response, I loadbalancer forces the workers each time
to retry, and when they timeout I got my 503.
The timeout can be tuned with defining a socket_timeout for the worker.
I would suspect that ones they are in error, I should get immediately a 503
response. And that after 60 seconds the workers will retry (with the recover
time)
Is this a bug, or do I need to configure something.
Thx for your help.
How to simmulate :
Drop packets on the your jboss application server with iptables.
# iptables -A INPUT -s (apache webserver) -p tcp --destination-port (port
jboss) -j DROP
Basic config
worker.list=applb
# Define a worker using ajp13
worker.worker1.port=8009
worker.worker1.host=backend1
worker.worker1.type=ajp13
worker.worker1.lbfactor=1
worker.worker1.socket_timeout=15
worker.basic.socket_keepalive=true
# Define another worker using ajp13
worker.worker2.port=8009
worker.worker2.host=backend2
worker.worker2.type=ajp13
worker.worker2.lbfactor=1
worker.worker2.socket_timeout=15
worker.basic.socket_keepalive=true
# Define the LB worker
worker.applb.type=lb
worker.applb.balanced_workers=worker1,worker2
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
