Glad to hear, let us know how it goes!
On 2/14/12 3:05 AM, Hervé BARRAULT wrote:
Hi thanks for the answer.
I thought using queues (with vm protocol) and with your argument on
scalability confirms it.
Regards
Hervé
On Mon, Feb 13, 2012 at 11:01 PM, Matt Pavlovich wrote:
I recommend using Qu
Hi thanks for the answer.
I thought using queues (with vm protocol) and with your argument on
scalability confirms it.
Regards
Hervé
On Mon, Feb 13, 2012 at 11:01 PM, Matt Pavlovich wrote:
> I recommend using Queues, since Durable Subscriptions can't scale on the
> consumer side (JMS spec only
I recommend using Queues, since Durable Subscriptions can't scale on the
consumer side (JMS spec only allows for one connection per subscriptionId).
Another option would be to use a Camel route to help filter the messages
based on your selector, so you only get messages into queues as needed.
Hi,
is there no advice to send a message to multiple consumers using activeMQ ?
Regards
Hervé
On 2/2/12, Hervé BARRAULT wrote:
> Hi,
> I would multicast messages to different (dynamically determined) consumers.
>
> I'm asking myself if it is more efficient to use multiple queues or use a
> topic
Hi,
I would multicast messages to different (dynamically determined) consumers.
I'm asking myself if it is more efficient to use multiple queues or use a
topic with durable subscription and selectors (I am using persistence).
I would say topics reduce the number of persisted messages but i am afra
