<h1>Java EE MDB Remote Failover Static Example</h1>
<p>This example shows you how to send a message to an MDB that is configured to consume from a live/backup pair.</p>
<p>The example will send deploy a simple MDB to one Wildfly instance. Then it will send a message to the live server of the live/backup pair
which will be consumed by the MDB after which the MDB will send a reply message which will be consumed by the example program. Then the live
server will be stopped so that the backup takes over and the process will be repeated.</p>
<p>Unlike the "Java EE MDB Remote Failover Example," this example uses a "static" configuration for finding all the nodes. In other words
it doesn't use UDP multicast for server discovery.</p>
<p>The example leverages the JBoss Arquillian framework to run a WildFly instance and deploy the MDB.</p>
<h2>Example step-by-step</h2>
<p><i>download WildFly 8.0.0.Final from <ahref="http://wildfly.org/downloads/">here</a> and install.</i></p>
<p><i>set the JBOSS_HOME property to point to the WildFly install directory</i></p>
<p><i>type <code>mvn verify</code> from the example directory to run</i></p>
<ol>
<li>First we need to get an initial context so we can look-up the JMS connection factory and destination objects from JNDI. This initial context will get it's properties from the <code>jndi.properties</code> file in the directory <code>config</code></li>
<li>And finally, <b>always</b> remember to close your JMS connections and resources after use, in a <code>finally</code> block. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects</li>