]
Jan Kašík commented on MODCLUSTER-675:
--------------------------------------
[~jfclere] I don't have a standalone reproducer, I run it as a test in mod_cluster
testsuite. I can post a link to the test if you want. I also edited the environment field
and added platform I spotted this issue on.
Failover scenario is not performed with httpd balancer - balancer
fails to respond
----------------------------------------------------------------------------------
Key: MODCLUSTER-675
URL:
https://issues.jboss.org/browse/MODCLUSTER-675
Project: mod_cluster
Issue Type: Bug
Components: Native (httpd modules)
Affects Versions: 1.3.8.Final
Environment: RHEL 7, CentOS 7 on x86_64 platform
Reporter: Jan Kašík
Assignee: Jean-Frederic Clere
Priority: Blocker
Attachments: error_log
When second request in failover scenario is made to check whether the failover was done,
server fails to respond. With Undertow as a balancer, this behavior cannot be reproduced.
When I replace the jvmroute part by worker which is still alive, I got expected response.
{noformat}# curl -v --cookie
"JSESSIONID=54yxdncGr5im0fBLqIIUMon0klbS66X16aYC_cVW.jboss-eap-7.2-3"
http://172.17.0.2:2080/clusterbench/jvmroute
* About to connect() to 172.17.0.2 port 2080 (#0)
* Trying 172.17.0.2...
* Connected to 172.17.0.2 (172.17.0.2) port 2080 (#0)
> GET /clusterbench/jvmroute HTTP/1.1
> User-Agent: curl/7.29.0
> Host: 172.17.0.2:2080
> Accept: */*
> Cookie: JSESSIONID=54yxdncGr5im0fBLqIIUMon0klbS66X16aYC_cVW.jboss-eap-7.2-3
>
* Empty reply from server
* Connection #0 to host 172.17.0.2 left intact
curl: (52) Empty reply from server
{noformat}