Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
MIME-Version: 1.0
In-Reply-To: <1510694002340-0.post@n4.nabble.com>
References: <1510694002340-0.post@n4.nabble.com>
From: Justin Bertram <jbertram@redhat.com>
Date: Tue, 14 Nov 2017 15:25:46 -0600
Message-ID: <CAF+kE=T0tsFcMT0NUgfe41CmM5yY9tpoX1SBOy+RDh9VwWgkVg@mail.gmail.com>
Subject: Re: ActiveMQ Artemis on AWS
To: users@activemq.apache.org
Content-Type: multipart/alternative; boundary="001a113ceeb2c3f2b0055df807d7"
archived-at: Tue, 14 Nov 2017 21:25:53 -0000

--001a113ceeb2c3f2b0055df807d7
Content-Type: text/plain; charset="UTF-8"

There are lots of JGroups protocols that might be useful in this scenario.
Have you looked at AWS_PING [1]?


Justin

[1] http://meltmedia.github.io/jgroups-aws/

On Tue, Nov 14, 2017 at 3:13 PM, Sakthi <msg2sakthi@gmail.com> wrote:

> Hi,
>
> We are migrating our applications to AWS environment.
> We have Artemis cluster Master/Slave and we are trying to configure it in
> AWS environment.
> Artemis uses the <group-address> for the clustering which is Class D ip
> address.
> But AWS doesn't seem to be allow the Class D ip address to broadcast the
> message to the group.
>
> Master and Slave are in different VM, so we are not able to use the
> jgroups-file as it requires common folder for the both the servers to
> access.
>
> Any help or suggestion are appreciated. Thanks.
>
> Sakthi S
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
> f2341805.html
>

--001a113ceeb2c3f2b0055df807d7--