title: JBoss EAP 6.2 any-address and Netty for remote JMS MDBs
body: <p>I am running <code>JBoss EAP 6.2</code> (embedded <code>HornetQ 2.3.12.Final</code>) as a <strong>standalone Messaging server</strong> that will host JMS Queues and Topics.</p>
  
  <p>There will be other JBoss servers that remotely connect to the Messaging Server's Queues and Topics.  </p>
  
  <p>Using this Stackoverflow answer: <a href="https://stackoverflow.com/a/6971854/463196">Binding JBoss AS 7 to all interfaces</a></p>
  
  <p>I made the following change to my <code>standalone-full.xml</code> configuration:</p>
  
  <pre><code>&lt;interfaces&gt;
      ...
      &lt;interface name="public"&gt;     
  &lt;!--&lt;inet-address value="${jboss.bind.address:127.0.0.1}"/&gt;--&gt;
          &lt;any-address/&gt;
      &lt;/interface&gt;
  &lt;/interfaces&gt;
  </code></pre>
  
  <p>After making this change, I can successfully connect from other JBoss servers via port 4447 (JBoss Remoting) and writing JMS Client code (ConnectionFactory, Connection, MessageProducer, etc). </p>
  
  <p>JBoss log has the following, which is reassuring:</p>
  
  <pre><code>[org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: 
  Listening on 0.0.0.0:4447
  </code></pre>
  
  <p><strong>However, I cannot connect via a remote MDB. :-( I need to figure this out because we do MDBs and not JMS Client code.</strong>  </p>
  
  <p>I looked at my JBoss log, and see the following <strong>error</strong>:</p>
  
  <pre><code>HQ121005: Invalid "host" value "0.0.0.0" detected for "netty" connector. 
  Switching to "ptenn-fc20.arbfile.org". If this new address is incorrect please 
  manually configure the connector to use the proper one.
  </code></pre>
  
  <p>I looked through the <code>&lt;subsystem xmlns="urn:jboss:domain:messaging:1.4"&gt;&lt;hornetq-server&gt; ...</code> section and did not see anything about how to specify a different address for the "netty" connector.  </p>
  
  <p>It definitely seems that Netty is using the public interface that I specified, I'm puzzled as to why JBoss Remoting (on port 4447) is fine listening on <code>0.0.0.0</code>, but Netty (on port 5445) is not.  </p>
  
  <p>If anyone has any ideas, insight, or suggestions, I would sincerely appreciate it. :-)</p>
  
  <p>Thanks,</p>
  
  <p>Philip</p>