[JBoss JIRA] (MODCLUSTER-676) Failover scenario is not performed with httpd balancer - balancer fails to respond
by Jan Kašík (Jira)
Jan Kašík created MODCLUSTER-676:
------------------------------------
Summary: Failover scenario is not performed with httpd balancer - balancer fails to respond
Key: MODCLUSTER-676
URL: https://issues.jboss.org/browse/MODCLUSTER-676
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
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, 12 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 commented on MODCLUSTER-675:
--------------------------------------
[~jfclere] I attached configuration of HTTPD balancer and one particular Wildfly worker. Reproducing this should be fairly easy now.
> 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, 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.12.1#712002)
5 years, 12 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:
---------------------------------
Attachment: wildfly-16.0.0.Beta1-SNAPSHOT.zip
httpd.zip
> 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, 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.12.1#712002)
5 years, 12 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 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}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 12 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:
---------------------------------
Environment: RHEL 7, CentOS 7 on x86_64 platform
> 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}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 12 months
[JBoss JIRA] (MODCLUSTER-675) Failover scenario is not performed with httpd balancer - balancer fails to respond
by Jean-Frederic Clere (Jira)
[ https://issues.jboss.org/browse/MODCLUSTER-675?page=com.atlassian.jira.pl... ]
Jean-Frederic Clere commented on MODCLUSTER-675:
------------------------------------------------
[~jkasik] obviously there is a problem I need to get someone to work on a reproducer, if you can't provide one ;-)
What is platform/os where the problem occurs?
> 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
> 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}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 12 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 edited comment on MODCLUSTER-675 at 12/4/18 3:22 AM:
---------------------------------------------------------------
This is the line it prints in error_log after I got that empty response:
{noformat}
[Tue Dec 04 08:18:34.639870 2018] [core:notice] [pid 34364] AH00052: child pid 39689 exit signal Segmentation fault (11)
{noformat}
This was the curl command:
{noformat}
curl -v --cookie "JSESSIONID=54yxdncGr5im0fBLqIIUMon0klbS66X16aYC_cVW.jboss-eap-7.2-3" http://172.17.0.2:2080/clusterbench/jvmroute
{noformat}
I also attached whole error_log which contains little bit of noise...
was (Author: jkasik):
This is the line it prints in error_log after I got that empty repsonse:
{noformat}
[Tue Dec 04 08:18:34.639870 2018] [core:notice] [pid 34364] AH00052: child pid 39689 exit signal Segmentation fault (11)
{noformat}
I also attached whole error_log which contains little bit of noise...
> 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
> 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}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years
[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:
---------------------------------
Attachment: error_log
> 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
> 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}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years
[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 commented on MODCLUSTER-675:
--------------------------------------
This is the line it prints in error_log after I got that empty repsonse:
{noformat}
[Tue Dec 04 08:18:34.639870 2018] [core:notice] [pid 34364] AH00052: child pid 39689 exit signal Segmentation fault (11)
{noformat}
I also attached whole error_log which contains little bit of noise...
> 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)
6 years
[JBoss JIRA] (MODCLUSTER-675) Failover scenario is not performed with httpd balancer - balancer fails to respond
by Jean-Frederic Clere (Jira)
[ https://issues.jboss.org/browse/MODCLUSTER-675?page=com.atlassian.jira.pl... ]
Jean-Frederic Clere commented on MODCLUSTER-675:
------------------------------------------------
[~jkasik] "Empty reply from server", that only occurs when httpd crashes or does something really wrong, please add the error_log file to the case.
> 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)
6 years