[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-318) Make connector address user configurable
Radoslav Husar (JIRA)
issues at jboss.org
Tue Jan 5 16:33:00 EST 2016
[ https://issues.jboss.org/browse/MODCLUSTER-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145210#comment-13145210 ]
Radoslav Husar commented on MODCLUSTER-318:
-------------------------------------------
{quote}Also it is likely to be the cause of MODCLUSTER-91.{quote}
I don' think so, MODCLUSTER-91 is about adding extra logic to infer the actual address if any local address was used for binding, also the issue is 1 year older than the other fix.
{quote}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.{quote}
If I am understanding the user request correctly and we do need to add support for overriding the address behind NAT/port-forward/container/etc, we shouldn't need to add the support to fiddle with the host resolution.
> 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: Radoslav Husar
>
> 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)
More information about the mod_cluster-issues
mailing list