[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-318) make connector address user configurable

[James Livingston (JIRA)]

    [ https://issues.jboss.org/browse/MODCLUSTER-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144188#comment-13144188 ] 

James Livingston commented on MODCLUSTER-318:
---------------------------------------------

This would also be useful to handle the case when there is a NAT between httpd and the backend, in which case the connector binding address is not the address that httpd can reach it on. That has been brought up a few times in the forum such as https://developer.jboss.org/thread/249888

> make connector address user configurable
> ----------------------------------------
>
>                 Key: MODCLUSTER-318
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-318
>             Project: mod_cluster
>          Issue Type: Feature Request
>    Affects Versions: 1.2.1.Final
>            Reporter: Aleksandar Kostadinov
>            Assignee: Paul Ferraro
>
> MODCLUSTER-168 introduced a change that broke some existing working configurations relying on using IP instead of a hostname. Also it is likely to be the cause of MODCLUSTER-91.
> To have everybody happy, this needs to be made configurable, perhaps a system property that user can set to force a particular IP or hostname. It would also be very useful if there is a special value that makes the behavior same as before the changes in MODCLUSTER-168. For example setting the value to -1 would return the original behavior.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)