Yes, one group is tied to a single consumer no matter how many of those are
there.
Regards
--
Dejan Bosanac - http://twitter.com/dejanb
-
The experts in open source integration and messaging - http://fusesource.com
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://
Is it also guaranteed with the Spring DefaultMessageListenerContainer when
the number of active consumer can vary over the time?
Regards
--
View this message in context:
http://activemq.2283324.n4.nabble.com/JMSXGroupID-timeout-tp3934661p4265945.html
Sent from the ActiveMQ - User mailing list ar
There is no one-to-one mapping between groups and consumers, it's just that
messages from one group are guaranteed to be processed by a single consumer.
Regards
--
Dejan Bosanac - http://twitter.com/dejanb
-
The experts in open source integration and messaging - http://fusesource.
It seems that I was wrong thinking that there will be one consumer for every
groupId, but only a mapping between the groupId hash and the max available
consumers, thus there is no real need for cleaning the mapping
groupId-to-consumer.
http://stackoverflow.com/questions/703659/activemq-message-gro
Hi Dejan,
We also have the need of Message Group closing on a timeout as we never know
in a message if this is the last one or not, thus we end up with a big
amount of consumers as we use an order id as the groupId.
Is there really no other way to close a consumer than from within the
message (th
Hi Roger,
you can always explicitly "close" a message group
http://activemq.apache.org/message-groups.html#MessageGroups-ClosingaMessageGroup
Timeout also makes sense, can you log it in Jira, so it can be considered as
an enhancement in future implementations.
Regards
--
Dejan Bosanac - http:/
