JBoss EAP 6 dynamic ports uses default server network interface instead of dedicated interface (jboss.bind.address)

Solution Unverified - Updated -

Issue

We want to manage multiple clustered JBoss AppServer instances using the default ports such that each JBoss instance gets its own network interface as specified in ifconfig

In our configuration we have two servers and on each server we have

  • a single interface
  • configured virtual interfaces for apache httpd and JBoss EAP
  • the JBoss EAP mod_cluster proxy-list references the two apache instances
  • JBoss EAP interfacing with remote databases and messaging providers
                         +-------------------+
                         |eth0: 10.20.30.101 |
                         |                   |
                    +--->|httpd:10.20.30.102 |
                    |    |                   |               10.48.212.206
                +---|    |jboss:10.20.30.103 |               +--------------+
   client       |   |    +-------------------+-------------->|              |
   +------->    |LB |                                        |:3306 mysql   |
                |   |                                        |:5432 postgres|
                +---+    +-------------------+-------------->|              |
                    |    |eth0: 10.20.48.101 |               +--------------+
                    |    |                   |
                    +--->|httpd:10.20.48.102 |
                         |                   |
                         |jboss:10.20.48.103 |
                         +-------------------+

For instance on one node we have set the bind address for the different components to jboss.bind.address

standalone-full-ha.xml:            <wsdl-host>${jboss.bind.address:10.20.30.103}</wsdl-host>
standalone-full-ha.xml:            <inet-address value="${jboss.bind.address.management:10.20.30.103}"/>
standalone-full-ha.xml:            <inet-address value="${jboss.bind.address:10.20.30.103}"/>
standalone-full-ha.xml:            <inet-address value="${jboss.bind.address.unsecure:10.20.30.103}"/>

netstat shows the default interface is being used for mod_cluster, database, and WebSphere MQ communications

netstat -lantp| grep java
.. ..
tcp        0      0 10.20.30.103:9999           0.0.0.0:*                   LISTEN      26381/java          
.. .. ..
tcp        0      0 10.20.30.103:8009           0.0.0.0:*                   LISTEN      26381/java          
tcp        0      0 10.20.30.101:49877          10.48.212.206:5432          ESTABLISHED 26381/java         
tcp        0      0 10.20.30.101:8009           10.33.23.110:3306           ESTABLISHED 26381/java 
tcp        0      0 10.20.30.101:49529          10.20.48.102:6666           ESTABLISHED 26381/java   

How can I get JBoss EAP to use the interface specified for -b for all communication in the JBoss java process? I want all the communications to the database(s) and mod_cluster to use the interface set for jboss.bind.address but it seems to be using eth0
I plan to add multiple standalone instances in the future and would like to use the default ports and not port-offset

Environment

Red Hat JBoss Enterprise Application Platform (EAP) 6.0.1, 6.1.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.