[
https://issues.apache.org/jira/browse/AMQ-4607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-4607:
----------------------------
Issue Type: Improvement (was: Bug)
> network connectors - new messageTTL and consumerTTL - split usage of
> networkTTL for mesh topology
> -------------------------------------------------------------------------------------------------
>
> Key: AMQ-4607
> URL: https://issues.apache.org/jira/browse/AMQ-4607
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.8.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Labels: configuration, configuration-addition, mesh,
> networkConnector, networkTTL
> Fix For: 5.9.0
>
>
> currently networkTTL in a networkConnector (default=1) means that a message
> can go one hop and demand (or info about a consumer) can go one hop.
> In a network (A<>B) messages and consumers can flow.
> In a linear network (A<>B<>C) networkTTL needs to be 2 for messages and
> consumers to flow two hops from A to C.
> In a mesh topology, (A<>B<>C<A>) a networkTTL=1 for consumers makes sense
> because there is at most one hop. However for messages, networkTTL > 1 is
> necessary if consumers need to hop around between brokers. Imagine a consumer
> on A which pulls messages to A from B, then the consumer moves to C, messages
> now need to hop again from A to C. This can repeat, essentially
> messageTTL(networkTTL) needs to be infinite.
> With consumerTTL > 1 in a mesh, managing demand for proxy (demand) consumers
> and proxy proxy consumers becomes very difficult.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
