[
https://issues.apache.org/jira/browse/AMQ-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dejan Bosanac updated AMQ-2711:
-------------------------------
Fix Version/s: (was: 5.4.2)
5.5.0
> conduitSubscriptions flag on networkConnector element should only affect
> queues, not topics
> -------------------------------------------------------------------------------------------
>
> Key: AMQ-2711
> URL: https://issues.apache.org/jira/browse/AMQ-2711
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Connector
> Affects Versions: 5.3.1
> Reporter: Fintan Bolton
> Fix For: 5.5.0
>
>
> In the doc for 'Networks of Brokers',
> http://activemq.apache.org/networks-of-brokers.html, it says that it is
> sometimes useful to disable {{conduitSubscriptions}} for queues, because this
> gives you a better load balancing effect when consumers are attached to
> various points in the broker network. The only trouble is, currently it does
> not seem practical to disable {{conduitSubscriptions}}, because this almost
> inevitably causes trouble with topics. That is, it can easily happen that
> topic messages are duplicated, if {{conduitSubscriptions}} is set to
> {{false}}.
> It seems like it would be better if topic subscriptions where *always*
> treated as conduits and the {{conduitSubscriptions}} attribute only affected
> queue subscriptions. That way, you could happily disable conduits for queues
> while leaving it enabled for topics.
> A bit of investigation is probably needed, however, to make sure that there
> aren't any edge cases where you might actually want to disable conduit
> subscriptions for topics.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
