Hi Tim , I have tried with the graceful shutdown by not using kill any more but still it's on the same way of dealing the consumer thread block.
you can find the new switch log here : https://gist.github.com/areddy7021/e0e3a6c89fc974ce3031e326c060acca I have switched like this way ..started with Broker A as master and B as slave ..-- > everything is fine Broker A service down and Broker B as new master -- > Producer is fine and Consumer started throwing exception and still consumed even after the switch since some buffered messages in prefetch buffer and after that inactivity monitor started throwing up and connection state in in blocked state in jconsole. Broker B service down and Broker A as new master ---> Producer no issues as usual. Consumer started showing some log in attempt to connect to new master but its not done with the inactivity log. The above gist log is for this scenario. Thanks, Akhil. -- View this message in context: http://activemq.2283324.n4.nabble.com/JMS-exception-during-the-Failover-tp4716047p4716660.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
