[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-675) Failover scenario is not performed with httpd balancer - balancer fails to respond

[Jan Kašík (Jira)]

    [ https://issues.jboss.org/browse/MODCLUSTER-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13669771#comment-13669771 ] 

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)