[
https://issues.apache.org/jira/browse/ARTEMIS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16311473#comment-16311473
]
Gary Tully commented on ARTEMIS-853:
------------------------------------
if MaxConsumes=1 did not error with an exception and retained the consumer as
pending it would be like the exclusive consumer.
With the exclusive consumer feature, the second or low priority consumer is
valid, just not getting any messages. Only when the first consumer goes away
does dispatch fallback to the second consumer.
MaxConsumes=1 could work but the client will then have to deal with retrys and
timeout and error logs filling up etc.
The original (way back) 5.x use case came from having a HA cluster of active
ejb servers with mdbs pointing to the broker, only one should get messages.
> Support for exclusive consumers
> -------------------------------
>
> Key: ARTEMIS-853
> URL: https://issues.apache.org/jira/browse/ARTEMIS-853
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: Broker
> Reporter: Matt Pavlovich
>
> Artemis should support a consumer feature where a single consumer receives
> all messages, even when multiple consumers are present. This capability
> maintains message ordering while allowing a HA consumer.
> ActiveMQ 5.x supports this, as does IBM MQ, Tibco EMS, etc.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
