title: Clustered Messaging (HornetQ) unable to start
body: <p>I'm running Wildfly 8.1, and am trying to get a standalone (non-domain) cluster up and running using the <code>standalone-full-ha.xml</code> configuration.  I've followed several clustering guides, including this one, but am having limited success.  I can get the cluster working if I use the <code>standalone-ha.xml</code> configuration, but this configuration does not include HornetQ for JMS messaging.  When I attempt the <code>standalone-full-ha.xml</code> configuration, however, I see the following in the logs:</p>
  
  <pre><code>10:40:33,079 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221006: Waiting to obtain live lock
  10:40:33,112 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221013: Using NIO Journal
  10:40:33,168 INFO  [io.netty.util.internal.PlatformDependent] (ServerService Thread Pool -- 60) Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system unstability.
  10:40:33,206 INFO  [org.jboss.as.jacorb] (MSC service thread 1-8) JBAS016328: CORBA Naming Service started
  10:40:33,243 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221043: Adding protocol support CORE
  10:40:33,246 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
  10:40:33,251 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221043: Adding protocol support AMQP
  10:40:33,255 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221043: Adding protocol support STOMP
  10:40:33,478 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory /Volumes/Untitled/Servers/wildfly-8.1.0.Final/standalone/deployments
  10:40:33,589 INFO  [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.4.Final
  10:40:33,620 INFO  [org.hornetq.core.server] (Thread-0 (HornetQ-server-HornetQServerImpl::serverUUID=a8a0aba8-1664-11e4-a805-3703f1c18bf5-370179839)) HQ221031: backup announced
  10:40:38,301 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221034: Waiting to obtain live lock
  </code></pre>
  
  <p>It just hangs at the "Waiting to obtain live lock" message.  The server never indicates that it is started, and I am unable to access the administration console.  Here is what I've been trying...</p>
  
  <ol>
  <li>Get a stock Wildfly 8.1 distribution and unpack it</li>
  <li>Start node 1 by issuing the command <code>./standalone.sh -c standalone-full-ha.xml -Djboss.node.name=nodeA</code></li>
  <li>Start node 2 by issuing the command <code>./standalone.sh -c standalone-full-ha.xml -Djboss.node.name=nodeB -Djboss.socket.binding.port-offset=100</code></li>
  </ol>
  
  <p>When I do this, however, I see the message in the log that I described above, and the server never completes startup.</p>
  
  <p>Am I doing something wrong?  Are there additional steps I need to take to get clustered messaging and Wildfly to work as expected?</p>