Yes our Consumers are always up and running and there were actually two subscribers at the time of this issue we have seen with stuck messages. This is more seems to happen very frequently with 5.15.0 version causing panic withing the team on whether its good to set up network of brokers or not. I used " rebalanceClusterClients" after reading a blog post and did not realize that priorityBackup negates it. I removed rebalanceClusterClients from our config now.
What other parameters can I watch to see why this happens frequently on different subscribers ? Also we seem to have constant errors on user not authenticated, even though same user is able to process messages once we re-start the JMS brokers. Thank you for your time ! -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
