Some news on that: in the meantime, we have switched to only using static bridges in our project for connection of the mobile brokers to the back office. Is much more stable now.
However, there is still some problem which shows up now and then: sometimes the back office broker "forgets" to start the responder end of the duplex="true" bridge. In this case there is no consumer on the respective queues in the backoffice broker, an the network connector on the mobile broker doesn't get an active bridge, although the connection is there (and the duplex="false" bridge for the direction mobile->back office works absolutely fine). Happens in one out of ~ 500 reconnections. I have tested this by turning up and down the network interface in an endless loop on one of the mobile target systems. So there still seems to be some instability when building the duplex bridge, even for static bridges. I have a "workaround" solution by monitoring the mobile broker via JMX beans, checking whether the duplex network connector has an active bridge when the connection is there. If not, the activemq-osgi bundle is restarted, which heals the problem. I'm not sure whether is makes sense to create a Jira issue for that. Regards, Jochen -- View this message in context: http://activemq.2283324.n4.nabble.com/Network-of-brokers-consumers-not-synchronized-tp4718852p4728365.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.