When a JMS connection with more than one producer session looses the underlying TCP connection to the broker auto reconnect (failover) is not working properly. After the reconnect attempt no new messages will be sent.
When only one producer session is used, reconnect apparently works as expected.
I attached a maven project with a test case where the TCP connection is dropped by the broker to provoke the reconnect attempt. In most cases when I run the test class the testAutoReconnectWith2ProducerSessions() stops sending messages after the first reconnect attempt. Maybe there occurs some qpid internal race condition.