Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <32304498.43631279281653306.JavaMail.jira@thor>
Date: Fri, 16 Jul 2010 08:00:53 -0400 (EDT)
From: =?UTF-8?Q?Dirk_Alexander_Sch=C3=A4fer_=28JIRA=29?= <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Issue Comment Edited: (AMQ-2829) HealthCheck for hardware
 loadbalancers
In-Reply-To: <30003459.42791279208031798.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/activemq/browse/AMQ-2829?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D60=
685#action_60685 ]=20

Dirk Alexander Sch=C3=A4fer edited comment on AMQ-2829 at 7/16/10 7:59 AM:
----------------------------------------------------------------------

so we could say: it's not a bug, it's a feature... ;)

      was (Author: dialsc):
    so we could say: it's not a bug, it's feature... ;)
 =20
> HealthCheck for hardware loadbalancers
> --------------------------------------
>
>                 Key: AMQ-2829
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2829
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker
>         Environment: ALL
>            Reporter: Dirk Alexander Sch=C3=A4fer
>            Assignee: Gary Tully
>            Priority: Minor
>             Fix For: 5.4.0
>
>         Attachments: com.swisscom.ei.commons.activemq.zip, jetty.xml
>
>
> hi there,
> we had the problem that we were not able to integrate our network of brok=
ers in our cluster setup where a hardware loadbalancer was in front of the =
cluster. as the loadbalancer needs to run health checks against each node i=
n the cluster, we needed to find a way to offer an endpoint the loadbalance=
r could send its probe requests to.
> we decided to develope a little web application that returns "pong" if th=
e jms provider is available, "offline" else. we've created a webapp that ca=
n be deployed in the jetty that comes with activemq. i attach the whole ecl=
ipse project ziped to this issue. i haven't cleaned it so it will not fitt =
into the activemq package hierarchy but it should be enough to get an idea =
of how we did it. i also attach the modified jetty.xml were we added the we=
bapp in order to become it loaded.
> it might look a bit oversized as it is based upon spring web mvc, spring =
security and tiles but our intention was to be able to put further administ=
rative functionality into the web app once needed.
> how it works: a consumer as well as a producer are being created during t=
he startup of the app. the consumer makes sure that messages get dispatched=
 and do not fill the queue, allthough the messages are marked none-persiste=
nce and have a ttl of 5 secs, just to be sure. if a check request comes in =
(/lbProbe/ping.htm) the app tries to put a message into the queue (the queu=
e name is configurable through spring). if this succeeds, the OK-result wil=
l be returned, otherwise the NOT-OK-result. both are configurable through s=
pring.
> known bugs: if one deletes the queue the app is using through e.g. the ad=
min web app, the check will strill return OK.
> things to beware of: the name of the queue the webapp uses should be conf=
igured in the excludes of the networkConnector settings ;)

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.