[
https://jira.jboss.org/jira/browse/MODCLUSTER-109?page=com.atlassian.jira...
]
Jean-Frederic Clere commented on MODCLUSTER-109:
------------------------------------------------
Looking to the log file the only thing I see is
proxy: AJP: attempt to connect to 192.168.1.141:8009 (192.168.1.141) failed
That doesn't correspond to the explainations:
192.168.1.101:http load balancer, 192.168.1.102:node1, 192.168.1.103:node2
On you explainations:
"1. START: [Mon Oct 26 16:27:04 2009] - [Mon Oct 26 16:29:49 2009]
2. KILL NODE1,: I set <property name="flushPackets">true</property>,
it seems working, without 503 node2 serving the request
3. RESTART NODE1,THEN KILL NODE2: [Mon Oct 26 16:35:32 2009] - [Mon Oct 26 16:36:00 2009],
--> 503, after ~20sec It begin to wok
"
Well that ~20 seconds looks a lot but if you kill a node it needs time to restart and to
send it configuration to httpd.
"sorry It works, I only forgot to add ProxyPass to httpd.conf. :( "
I don't get it.
You don't need a ProxyPass in most of the use case of mod_cluster.
503 Service Temporarily Unavailable
------------------------------------
Key: MODCLUSTER-109
URL:
https://jira.jboss.org/jira/browse/MODCLUSTER-109
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.2.GA
Environment: httpd+modcluster,seam 2.2.0GA,JBoss 5.1.0.GA
Reporter: Karl Max
Assignee: Jean-Frederic Clere
Attachments: error_log
When I use mod_cluster on startup/either node is failover sometimes I get 503 Service
Temporarily Unavailable error
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira