I didn't follow the bit about grouping your workers. You have N ActiveMQ
consumers, and the message group will be assigned to one (and only one) of
them. Where does grouping workers play into it?
Tim
On Mar 9, 2018 3:18 PM, "vramanx" wrote:
Thanks for the clarification Tim! From the documentati
Thanks for the clarification Tim! From the documentation, I thought that the
consumers have to be tagged with static GroupID which is then later set on
the producer side.
So on the consumer side we just need to group workers as a processing unit
and the system will pick an available group to assig
Agree.
Sorry for that.
Br, A.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
I believe the original author on this thread was using 5.x, but you're
using Artemis so it might be best to start a new thread. In any event,
it's generally not good manners to hijack someone else's thread with your
own issue. It usually confuses the original issue and delays resolution
for the t
Even if, would not make any difference in my case.
The topic consumer is the broker itself by diverting messages into queues.
But each queue has multiple consumers which process messages concurrently...
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Don't topic consumers process messages one by one by default?
Tim
On Mar 1, 2018 5:56 AM, "Archibald" wrote:
> I'm struggling with a similiar problem:
>
> I have one producer sending event messages.
> I have a couple of different consumers which shall react on those events.
> Producer is not aw
I'm struggling with a similiar problem:
I have one producer sending event messages.
I have a couple of different consumers which shall react on those events.
Producer is not aware of any consumers and as such publishes events to a
topic.
The broker is configured with diverts which split and forwa
Re-reading your original question, I realized that I assumed that you were
aware of the JMS-standard feature called message groups, which ensure that
all messages with a given group ID are consumed (in order) by a single
consumer. That feature will meet all of your requirements except for the
abili
The group id is dynamic. So we cant really have a set of consumers with a
pre-defined set of group ids.
One way to handle this is to spin up a singleton actor consumer for a group
id if none exists.
Will be great if ActiveMQ supports this concept of "dynamic group id" out of
the box so there is a
Message groups are tied to one and only one consumer (unless that consumer
disconnects, in which case a new consumer can be chosen). I'm not aware of
any feature that would allow any consumer to take the next message in the
group but only if no other message in the group is being processed, which
i
Is it possible to have a fixed set of consumers in a MessageGroup listening
to all the messages, but the processing will be sequential for a given group
id?
for example,
we have an order processing system and the group id is the order id.
messages for an order should be processed sequentially. as
11 matches
Mail list logo
