From jira-events at lists.jboss.org Mon Sep 16 06:07:04 2013
Content-Type: multipart/mixed; boundary="===============4202555686627862404=="
MIME-Version: 1.0
From: Weinan Li (JIRA) <jira-events at lists.jboss.org>
To: mod_cluster-issues at lists.jboss.org
Subject: [mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-356) BalancerMember
 directives cause httpd crash when using mod_cluster 1.2.x
Date: Mon, 16 Sep 2013 06:07:04 -0400
Message-ID: <JIRA.12499493.1377680902000.27178.1379326024500@jira02.app.mwc.hst.phx2.redhat.com>
In-Reply-To: JIRA.12499493.1377680902000@jira02.app.mwc.hst.phx2.redhat.com

--===============4202555686627862404==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable


    [ https://issues.jboss.org/browse/MODCLUSTER-356?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D128044=
19#comment-12804419 ] =


Weinan Li commented on MODCLUSTER-356:
--------------------------------------

Yeah if I restart httpd/EAP sometimes it will throw:

{code}
Error null sending STATUS command to min/10.0.1.13:10001, configuration wil=
l be reset: null
{code}

And this just happen during server restart to me. =


The httpd crashing stopped after I've upgrade mod_cluster to 1.2.6.Final in=
 httpd. No crashing anymore, and no error log from both EAP and httpd sides=
, and node could be seen correctly from '/mod_cluster-manager'. From wiresh=
ark analyse the CPING/CPONG of AJP port between EAP/httpd are fine.

But the "<title>503 Service Temporarily Unavailable</title>" still exists. =
The node is not serving.

I've also tried to upgrade mod_cluster in EAP side also to 1.2.6.Final and =
the problem still there.

Not sure where the problem could be. Because Wireshark doesn't understand t=
he MCMP in 10001 port, so it's hard for me to see if there are any problems.


                =

> BalancerMember directives cause httpd crash when using mod_cluster 1.2.x
> ------------------------------------------------------------------------
>
>                 Key: MODCLUSTER-356
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-356
>             Project: mod_cluster
>          Issue Type: Bug
>    Affects Versions: 1.2.4.Final
>         Environment: SLES-11-SP1 x86_64 running httpd 2.2.24 or 2.4.6 wit=
h any mod_cluster-1.2.x version and JBoss-AS-7.2.0.Final
>            Reporter: Marco Danti
>            Assignee: Jean-Frederic Clere
>              Labels: balancerMember, crash, httpd, mod_cluster
>
> httpd dumps core in mod_proxy_cluster.c if the httpd.conf file contains B=
alancerMember directives.
> this happens at least with the following two setups:
>  1) httpd-2.4.6 and mod_cluster-1.2.x
>  2) httpd-2.2.24 and mod_cluster-1.2.3.Final

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira

--===============4202555686627862404==--