We have 4 clients publishing to a virtual-topic, and 4 instances of an application with 15 consumers consuming messages from that topic.
The topic is running on two servers (A and B) with a duplex networkconencts from A to B. Thw transportConnector is set up with setUpdateClusterClientsOnRemove and setUpdateClusterClients to true. The failover configuration is as follows: Publishers: failover:(tcp://A)?randomize=false&backup=true&timeout=10&priorityBackup=true&maxReconnectDelay=10&maxReconnectAttempts=1&trackMessages=true Consumers: failover:(tcp://A)?randomize=false&backup=true&priorityBackup=true&maxReconnectDelay=10&maxReconnectAttempts=1 We deploy to half the instances of the modules at the time, so that we have no downtime. When stopping and deploying to A, we se that all publisher and consumers goes to B, but when A comes up again, one of the four publisher instances keeps publishing to B while the rest of the publishers, and all the consumers goes back to A. This results in a lot of messages never being consumed. The logs shows that the publisher successfully connects to A after A is up again, but this isntt reflected in where the mesages are published. Can anoyone see any reason for this? -- Audun Fauchald Strand
