A shutdown is treated different at the moment... it will send a notificatino to clients so they can reconnect on a backup node.
Try setting failoverOnShutdown=false.
Thanks for your support. I had tried that earlier itself without success. After few trials, now I found that the issue is due to presence of another connection factory entry with same name ("NettyConnectionFactory") in the xml. The following xml worked fine without any issues.
<configuration xmlns="urn:hornetq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:hornetq /schema/hornetq-jms.xsd"> <connection-factory name="NettyConnectionFactory"> <xa>false</xa> <connectors> <connector-ref connector-name="netty"/> </connectors> <entries> <entry name="/ConnectionFactory"/> </entries> <block-on-durable-send>true</block-on-durable-send> <block-on-acknowledge>true</block-on-acknowledge> <block-on-non-durable-send>true</block-on-non-durable-send> <retry-interval>1000</retry-interval> <reconnect-attempts>-1</reconnect-attempts> <confirmation-window-size>1048576</confirmation-window-size> <connection-ttl>120000</connection-ttl> <client-failure-check-period>30000</client-failure-check-period> <call-timeout>300000</call-timeout> </connection-factory> <queue name="DLQ"> <entry name="/queue/DLQ"/> </queue> <queue name="ExpiryQueue"> <entry name="/queue/ExpiryQueue"/> </queue> </configuration>
Can this be a bug?