Re: what value of networkTTL need to use for synchronous request and reply in network connectors

2018-02-14 Thread Gary Tully
In the event of connection failures there is a good chance of loosing messages. If you are about messages and replies then use real queues, maybe have a reply queue per process or per application and use selectors based on the correlation id if you need to multiplex. The lifetime of a temp queue

Re: what value of networkTTL need to use for synchronous request and reply in network connectors

2018-02-12 Thread Tim Bain
In any mesh network, I'd always recommend setting decreaseNetworkConsumerPriority=true. If you do that, and if clients will only ever connect to a single broker, then a networkTTL of 2 is fine, because the message will always traverse at most two brokers. However, if your consumers can disconnect