Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C95AE1.ECD0ECAD"
Subject: network of embedded brokers (in Glassfish)
Date: Wed, 10 Dec 2008 10:11:13 -0600
Message-ID: <BBB15F75F55BF743943A181FFEF8FBF2021C03E9@EXCHANGE2.biperf.com>
Thread-Topic: network of embedded brokers (in Glassfish)
Thread-Index: Acla4ex23bz+wex4QMKGLdsrBk26nA==
From: "Repko, Brian" <repko@BIWORLDWIDE.com>
To: <users@activemq.apache.org>

------_=_NextPart_001_01C95AE1.ECD0ECAD
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

We=20have=20had=20a=20number=20of=20issues=20with=20the=20genericjmsra=20a=
nd=20OpenMQ=20on
Glassfish=20V2
and=20are=20looking=20to=20switch=20to=20ActiveMQ=20(RAR/brokers).=20=20We=
=20have=20that
working=20now=20(and=20
I=20intend=20to=20put=20a=20blog=20together=20on=20that=20since=20Ramesh's=
=20standard=20blog=20is
quite=20old=20and=20
not=20really=20accurate).=20=20With=20ActiveMQ=20we=20can=20use=20both=20d=
irect=20JMS
producers/consumers=20
as=20well=20as=20MDBs=20(GF=20default=20components=20don't=20support=20dir=
ect=20consumers=20-
only=20MDBs
and=20MDBs=20in=20a=20cluster=20on=20a=20topic=20do=20once-per-cluster=20s=
emantics=20-=20not
once-per-server).
=20
We=20are=20now=20looking=20at=20our=20options=20for=20broker=20topologies=20=
and=20there=20in
lies=20my=20question.
=20
We=20have=20multiple=20clusters=20of=20application=20servers=20(2-4=20serv=
ers=20per
cluster)=20-=20each=20app=20
server=20cluster=20will=20get=20a=20cluster=20of=20brokers=20(probably=202=
=20but=20only=20for
failover).=20=20GF=20can=20create
a=20network=20of=20brokers=20on=20startup=20(external=20processes=20with=20=
cluster
configuration=20based=20on=20
the=20application=20server=20cluster).=20=20In=20trying=20to=20mimic=20tha=
t=20behaviour,=20I
was=20wondering=20if=20I=20can
configure=20the=20RAR=20to=20use=20a=20vm://=20broker=20so=20that=20client=
s=20in=20that=20server
connect=20to=20it,=20but=20
that=20those=202=20vm://=20brokers=20share=20the=20same=20data=20-=20can=20=
they=20do
store/forward=20to=20each=20other
or=20just=20work=20off=20a=20SAN=20or=20DB=20for=20persistence?=20=20What=20=
kind=20of=20connectivity
does=20a=20vm://
broker=20expose?
=20
We=20want=20it=20so=20that=20when=20one=20server=20does=20down,=20then=20t=
he=20other=20keeps
working=20on=20messages
(producers/consumers=20are=20duplicated=20on=20both=20servers)=20sent=20by=
=20the=20other
one=20but=20that=20haven't
been=20processed=20yet.
=20
Any=20suggestions=20or=20similar=20topologies=20that=20others=20know=20wor=
k?=20=20Just
trying=20to=20save=20myself
some=20time=20in=20testing=20various=20scenarios.
=20
Thanks,
Brian

This=20e-mail=20message=20is=20being=20sent=20solely=20for=20use=20by=20th=
e=20intended=20recipient(s)=20and=20may=20contain=20confidential=20informa=
tion.=20=20Any=20unauthorized=20review,=20use,=20disclosure=20or=20distrib=
ution=20is=20prohibited.=20=20If=20you=20are=20not=20the=20intended=20reci=
pient,=20please=20contact=20the=20sender=20by=20phone=20or=20reply=20by=20=
e-mail,=20delete=20the=20original=20message=20and=20destroy=20all=20copies=
.=20Thank=20you.
------_=_NextPart_001_01C95AE1.ECD0ECAD--