[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-675) Failover scenario is not performed with httpd balancer - balancer fails to respond
Jean-Frederic Clere (Jira)
issues at jboss.org
Sun Mar 29 05:32:18 EDT 2020
[ https://issues.redhat.com/browse/MODCLUSTER-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Frederic Clere updated MODCLUSTER-675:
-------------------------------------------
Fix Version/s: 1.3.12.Final
> Failover scenario is not performed with httpd balancer - balancer fails to respond
> ----------------------------------------------------------------------------------
>
> Key: MODCLUSTER-675
> URL: https://issues.redhat.com/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 Kasik
> Assignee: Jean-Frederic Clere
> Priority: Blocker
> Fix For: 1.3.12.Final
>
> Attachments: error_log, httpd.zip, wildfly-16.0.0.Beta1-SNAPSHOT.zip
>
>
> 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}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
More information about the mod_cluster-issues
mailing list