Failover using a JDBC Message Store and Virtual Topic can result in a lost message if queue is empty

Description:
A consumer connects to the broker and expresses interest in the virtual topic and the queue is created and empty
The consumer then disconnects
The broker is killed and the producer fails over to the next broker
The producer sends the message to the topic
The consumer reconnects to the broker, however it has no message waiting the virtual topic's queue

Symptom
The queue for the virtual topic is not automatically created during the failover.

Work around
A work around for this issue is to use startup destinations on the slave brokers if the destination is known.