I guess that a key point to have in the back of ones mind is that the
JMS Concepts of topic and queue are really mappings on to AMQP in Qpid.
By that I mean in AMQP there are concepts of exchanges, queues and
bindings between the exchange and queue - and consumers *always* receive
their
Hi all,
My requirement is to notify a cluster of nodes, when an event is occurred..
nodes will be different based on client Id, one client can have more than
one node...
In message broker, I will have one queue per client (Say queue1, queue2.. )
, and nodes will be listening to their relevant
On 02/10/2012 12:43, Sajith Kariyawasam wrote:
I realize that if one node(say node1) reads the message from the queue,
the message is gone, so that the other nodes (node1 and node2) will not be
notified..
Sorry, I may have pressed the key combination for send :-)
This is the full message.
Have you considered JMS durable subscriptions?
They are described here:
http://docs.oracle.com/javaee/1.3/jms/tutorial/1_3_1-fcs/doc/basics.html
On 2 October 2012 11:43, Sajith Kariyawasam saj...@gmail.com wrote:
Hi all,
My requirement is to notify a cluster of nodes, when an event is
Sajith,
As Phil mentioned, using durable subscriptions is one way of doing it.
You could also use Queues in this case as long as you use 1 queue per node.
When your client sends a message it will end up in all the nodes
interested in your message.
Lets say you send a message to the following
