Description of problem: mod_cluster only uses the default interface and this currently isn't configurable. Expected results: The proxy-list attribute is improved to allow a desired address/interface to be specified for the Jboss side of the proxy connection. Additional info: What looks to be the cause from org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler: private synchronized Socket getConnection() throws IOException { if ((this.socket == null) || this.socket.isClosed()) { this.socket = this.socketFactory.createSocket(); InetAddress address = this.socketAddress.getAddress(); if ( address instanceof Inet6Address && ((Inet6Address)address).isLinkLocalAddress()) { /* We need to work-around a java6 bug */ InetSocketAddress addr = new InetSocketAddress(address, 0); this.socket.bind(addr); this.socket.connect(this.socketAddress, this.socketTimeout); } else { // no socket bind. socket connected from default interface. this.socket.connect(this.socketAddress, this.socketTimeout); } this.socket.setSoTimeout(this.socketTimeout); this.localAddress = this.socket.getLocalAddress(); } return this.socket; } We need a way to change the bind address of this socket through the configuration of the modcluster subsystem
See https://issues.jboss.org/browse/WFLY-457 it is not fixed upstream
FYI - https://issues.jboss.org/browse/WFLY-457 is still open and targeted for 9.0.0.CR1
QA NACK as there is no RFE in https://issues.jboss.org/browse/EAP6 and WFLY issue is targeted for next major release.
This should be deferred to EAP7.
Dear Rado, could you create an EAP7 RFE Jira so as this bugzilla won't slip through the cracks? Thx :-)
This is already implemented (9.0.0.Alpha1) so no need for RFE.
Closed;Upstream https://issues.jboss.org/browse/WFLY-457