[JBoss JIRA] (MODCLUSTER-675) Failover scenario is not performed with httpd balancer - balancer fails to respond
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/MODCLUSTER-675?page=com.atlassian.jira.pl... ]
Radoslav Husar reassigned MODCLUSTER-675:
-----------------------------------------
Assignee: Jean-Frederic Clere (was: Radoslav Husar)
> 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
> Reporter: Jan Kašík
> Assignee: Jean-Frederic Clere
> Priority: Blocker
>
> 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.12.1#712002)
5 years, 4 months
[JBoss JIRA] (MODCLUSTER-675) Failover scenario is not performed with httpd balancer - balancer fails to respond
by Jan Kašík (Jira)
[ https://issues.jboss.org/browse/MODCLUSTER-675?page=com.atlassian.jira.pl... ]
Jan Kašík updated MODCLUSTER-675:
---------------------------------
Description:
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}
was:
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.
{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}
> 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
> Reporter: Jan Kašík
> Assignee: Radoslav Husar
> Priority: Blocker
>
> 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.12.1#712002)
5 years, 4 months
[JBoss JIRA] (MODCLUSTER-675) Failover scenario is not performed with httpd balancer - balancer fails to respond
by Jan Kašík (Jira)
[ https://issues.jboss.org/browse/MODCLUSTER-675?page=com.atlassian.jira.pl... ]
Jan Kašík updated MODCLUSTER-675:
---------------------------------
Summary: Failover scenario is not performed with httpd balancer - balancer fails to respond (was: Failover scenario is not performed with httpd balancer)
> 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
> Reporter: Jan Kašík
> Assignee: Radoslav Husar
> Priority: Blocker
>
> 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.
> {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.12.1#712002)
5 years, 4 months
[JBoss JIRA] (MODCLUSTER-675) Failover scenario is not performed with httpd balancer
by Jan Kašík (Jira)
Jan Kašík created MODCLUSTER-675:
------------------------------------
Summary: Failover scenario is not performed with httpd balancer
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
Reporter: Jan Kašík
Assignee: Radoslav Husar
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.
{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.12.1#712002)
5 years, 4 months