mod_cluster and WildFly through a NAT

[mylos78]

Hi all!

We are planning to use mod_cluster as front-end for a farm of JBoss application servers. The matter is that Apache Servers (hosting mod_cluster) will be outside the DMZ and there will be NAT between Apache and WildFly servers. Can you provide some initial guidelines for the configuration- f.e. I guess we should switch to a hostname based communication. How do we set it ? will that be sufficient ?

Thanks

Mylos

[rhusar]

Actually I don't really see how would that work.

The auto-magic UDP multicast discovery won't work, but you can statically configure list of reverse proxies in the AS/WildFly configuration ('proxies'). However, the reverse proxy connections to the backend servers are initiated by Apache/mod_cluster and since NAT masquerades the IP address it won't be able to route to those addresses. Neither if you configure static NAT/port forwarding, the AS/WildFly will advertise the address of the connector/listener which won't match the NAT's address.

[jameslivingston]

For anyone reading this in future, [MODCLUSTER-318] make connector address user configurable - JBoss Issue Tracker would help here, allowing you to configure the address httpd contacts JBoss/Wildfly on.