activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sebastian Rodriguez <srodrig...@gmail.com>
Subject ActiveMQ topology problem
Date Wed, 16 Dec 2009 17:22:13 GMT
Dear all,
I'm currently having a topology problem and I'm not so sure it can be handle
in the current situation.
I want to use the topology attached in the mail.
Basically I've a client server application, and I'm using activeMQ for some
notifications.
* Every client is connected in static mode to his local activeMQ (ActiveMQ
client in the diagram).
*The local activeMQ is connected to the network of brokers via a duplex
connection.
My servers are directly connected to the network of brokers via failover
protocol, as the brokers in the network of brokers are hosted by my servers.
The activeMQ in the network of brokers is connected in duplex mode too, as
there can be a firewall in between them.

This works great and as expected.

The problem comes when, in addition of that I want a "special" client, the
one on the right on the diagram.
Basically, I want that the messages sent from his activeMQ are received by
the ones in the network of brokers, but also to all the clients outside the
network of brokers.

Of course, when thinking about this issue, we though about network TTL. If I
enable the network TTL, yes, i will receive the messages from this special
client, but i'll receive double or triple messages coming from the network
of brokers.

The only solution that I've found so far is to include the activemq of this
special client into the network of brokers, but I don't think it's actually
a very good idea. The behavior of ActiveMQ, duplex connections and TTL is
the expected one?
Any recommendations to archive this topology?
Thank you very much for your help,

-- 
Sebastien Rodriguez

Mime
  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message