This topic has not yet been written. The content below is from the topic description.
34.2. Session reconnection Alternatively, the server might have actually been restarted after crashing or being stopped. In this case any sessions will no longer be existent on the server and it won't be possible to 100% transparently re-attach to them. In this case, HornetQ will automatically reconnect the connection and recreate any sessions and consumers on the server corresponding to the sessions and consumers on the client. This process is exactly the same as what happens during failover onto a backup server. Client reconnection is also used internally by components such as core bridges to allow them to reconnect to their target servers. Please see the section on failover Section 39.2.1, “Automatic Client Failover� to get a full understanding of how transacted and non-transacted sessions are reconnected during failover/reconnect and what you need to do to maintain once and only once delivery guarantees.