CLONE - Server cannot be shutdowned gracefully when reconnect-attempts is set to -1

In circumstances where a HornetQ resource adapter (RA) was configured to connect via a remote JBoss Messaging Server (JMS) instance and the resource adapter had <systemitem>reconnect-attempts</systemitem> set to <literal>-1</literal> (infinite), the server hosting the message-driven bean (MDB) could not be shut down cleanly if the remote server was not available. Potential consequences of this issue included loss of transactions being processed at the time the server was attempting to shut down. This issue has been resolved by changing the handling of the <literal>-1</literal> setting for <systemitem>reconnect-attempts</systemitem> so that reconnection attempts are stopped if the remote server is not available. In these circumstances the server hosting the MDB instance can now be shut down cleanly.