Re: ActiveMQ duplex network connector dead lock [5.13.1, 5.11.1]

Thanks for the response Tim! I would not mind to go with more complicated config as long as it works. Just my experience on AMQ config is very basic. I've seen some examples of using two non-duplex network connectors for 1-to-1 brokers. But I didn't find out similar examples for 1-to-many brokers.

Re: ActiveMQ duplex network connector dead lock [5.13.1, 5.11.1]

You can use two non-duplex connections, one from each broker. This is advantageous in some network configurations (e.g a pair of brokers) because it lets you reuse the same configuration on multiple brokers (with a little placeholder substitution) and disadvantageous in others (e.g. a hub-and-spok

How to monitor cluster updates from the client

I'm testing JMS applications in a NoB cluster to validate client are receiving updates as brokers join/leave the cluster; our openwire connector config: The client connection URL is below; this is just a virtual IP that proxies to a router and finds the nearest broker (all of this wo

ActiveMQ duplex network connector dead lock [5.13.1, 5.11.1]

Hi： We ran into this dead lock since upgrade to 5.11.1. In short, this dead lock happens on network connector when "duplex" is set to "true". For details of replicating this defect, see my earlier post here I also fo