[
https://issues.apache.org/jira/browse/QPID-8389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16999779#comment-16999779
]
Robert Godfrey commented on QPID-8389:
--------------------------------------
So "operational" vs. "live"... I can't say I'm particularly fond of "live", but
I think operational (or more specifically non-operational) gives the wrong
impression. If I think of something as being non-operational I think of it
being broken in some way. Active / non-active is clearly the best wording, but
active already means something else for consumers in Broker-J. Maybe
activated/standby?
In terms of factoring the increment/decrement stuff... I'm ok with that
In the test I actually wanted stuff prefetched and then returned when the
consumer closes... (or in the case of 0-9-1 the session closes :-) )
Having isNonLive (or isStandby) a derived attribute makes sense
> [Broker-J] Support the ability to limit the number of active consumers
> ----------------------------------------------------------------------
>
> Key: QPID-8389
> URL: https://issues.apache.org/jira/browse/QPID-8389
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
> Reporter: Robert Godfrey
> Assignee: Robert Godfrey
> Priority: Major
> Fix For: qpid-java-broker-8.0.0
>
>
> RabbitMQ supports an extension to queue.declare to designate that the queue
> will support only one "active" consumer, while keeping other consumers
> connected to act as a fast failover (see
> [https://www.rabbitmq.com/consumers.html#single-active-consumer]).
> We should add the ability for similar configuration to Broker-J
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
