[jboss-jira] [JBoss JIRA] (WFLY-8432) Support socket-binding attribute "client-mapping" in messaging subsystem

[ https://issues.jboss.org/browse/WFLY-8432?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFLY-8432: ----------------------------------- This causes issue when WildFly is behind a load balancer as the JMS client would use the host of the http-socket binding (localhost) instead going through the loadbalancer. If the config is: {code} <socket-binding name="http" port="${jboss.http.port:8080}"> <client-mapping destination-address="192.168.122.199" destination-port="8000"/> </socket-binding> {code} The http-connector transport configuration should use 192.168.122.199 and 8000 as host and port (instead of localhost and 8080). -- This message was sent by Atlassian JIRA (v7.2.3#72005)