Show Table of Contents
32.2. Session reconnection
If the server is restarted after crashing or being stopped, sessions will no longer exist on the server and it will not be possible to re-attach completely transparently.
In this case, HornetQ automatically reconnects the connection and recreates any sessions and consumers on the server based on the sessions and consumers of the client. (This process is identical to fail-over onto a backup server.) Client reconnection is also used internally by components such as core bridges to let them reconnect to their target servers. See Section 37.2.1, “Automatic Client fail-over” for a full explanation of how transacted and non-transacted sessions are reconnected during fail-over, and the requirements of once-and-only-once delivery guarantees.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.