title: Wildfly 9 - mod_cluster on TCP
body: <p>We are currently testing to move from Wildfly 8.2.0 to Wildfly 9.0.0.CR1 (or CR2 built from snapshot). The system is a cluster using mod_cluster and is running on VPS what in fact prevents it from using multicast.</p>
  
  <p>On 8.2.0 we have been using the following configuration of the modcluster that works well:</p>
  
  <pre><code>      &lt;mod-cluster-config proxy-list="1.2.3.4:10001,1.2.3.5:10001" advertise="false" connector="ajp"&gt;
            &lt;dynamic-load-provider&gt;
                &lt;load-metric type="cpu"/&gt;
            &lt;/dynamic-load-provider&gt;
        &lt;/mod-cluster-config&gt;
  </code></pre>
  
  <p>Unfortunately, on 9.0.0 proxy-list was deprecated and the start of the server will finish with an error. There is a terrible lack of documentation, however after a couple of tries I have discovered that proxy-list was replaced with proxies that are a list of outbound-socket-bindings. Hence, the configuration looks like the following:</p>
  
  <pre><code>      &lt;mod-cluster-config proxies="mc-prox1 mc-prox2" advertise="false" connector="ajp"&gt;
            &lt;dynamic-load-provider&gt;
                &lt;load-metric type="cpu"/&gt;
            &lt;/dynamic-load-provider&gt;
        &lt;/mod-cluster-config&gt;
  </code></pre>
  
  <p>And the following should be added into the appropriate socket-binding-group (full-ha in my case):</p>
  
  <pre><code>    &lt;outbound-socket-binding name="mc-prox1"&gt;
          &lt;remote-destination host="1.2.3.4" port="10001"/&gt;
      &lt;/outbound-socket-binding&gt;
      &lt;outbound-socket-binding name="mc-prox2"&gt;
          &lt;remote-destination host="1.2.3.5" port="10001"/&gt;
      &lt;/outbound-socket-binding&gt;
  </code></pre>
  
  <p>So far so good. After this, the httpd cluster starts registering the nodes. However I am getting errors from load balancer. When I look into /mod_cluster-manager, I see a couple of <strong>Node REMOVED</strong> lines and there are also many many errors like:</p>
  
  <pre><code>ERROR [org.jboss.modcluster] (UndertowEventHandlerAdapter - 1) MODCLUSTER000042: Error MEM sending STATUS command to node1/1.2.3.4:10001, configuration will be reset: MEM: Can't read node
  </code></pre>
  
  <p>In the log of mod_cluster there are the equivalent warnings:</p>
  
  <p><code>manager_handler STATUS error: MEM: Can't read node</code></p>
  
  <p>As far as I understand, the problem is that although wildfly/modcluster is able to connect to httpd/mod_cluster, it does not work the other way. Unfortunately, even after an extensive effort I am stuck.</p>
  
  <p>Could someone help with setting mod_cluster for Wildfly 9.0.0 without advertising? Thanks a lot.</p>