[jboss-jira] [JBoss JIRA] (WFLY-5840) mod_cluster proxies doesn't accept expressions

[Rafael Benevides (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rafael Benevides updated WFLY-5840:
-----------------------------------
    Description: 
proxy-list was deprecated in WFLY-457

Now I'm forced to use proxies but it doesn't accept expressions.

I want to create a customisable Docker image with where the modcluster ip can be configured at runtime

I'd like that Wildfly image to accept the following command but

_/subsystem=modcluster/mod-cluster-config=configuration:write-attribute(name=proxies,value=[${modcluster.host:modcluster}:${modcluster.port:80}])_


but if fails with:{color:red} "Services that may be the cause:" => ["jboss.outbound-socket-binding.\"${modcluster.host:modcluster}:${modcluster.port:80}\""]{color}

With /subsystem=modcluster/:add-proxy(host=${modcluster.host:modcluster},port=80) it fails with WFLYMODCLS0016: No IP address could be resolved for the specified host of the proxy.



  was:
proxy-list was deprecated in WFLY-457

Now I'm forced to use proxies but it doesn't accept expressions.

I want to create a customisable Docker image with where the modcluster ip can be configured at runtime

I'd like that Wildfly image to accept the following command but
```
/subsystem=modcluster/mod-cluster-config=configuration:write-attribute(name=proxies,value=[${modcluster.host:modcluster}:${modcluster.port:80}])
```

but if fails with: "Services that may be the cause:" => ["jboss.outbound-socket-binding.\"${modcluster.host:modcluster}:${modcluster.port:80}\""]

With /subsystem=modcluster/:add-proxy(host=${modcluster.host:modcluster},port=80) it fails with WFLYMODCLS0016: No IP address could be resolved for the specified host of the proxy.





> mod_cluster proxies doesn't accept expressions
> ----------------------------------------------
>
>                 Key: WFLY-5840
>                 URL: https://issues.jboss.org/browse/WFLY-5840
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Clustering
>    Affects Versions: 9.0.2.Final
>            Reporter: Rafael Benevides
>            Assignee: Paul Ferraro
>              Labels: mod_cluster
>
> proxy-list was deprecated in WFLY-457
> Now I'm forced to use proxies but it doesn't accept expressions.
> I want to create a customisable Docker image with where the modcluster ip can be configured at runtime
> I'd like that Wildfly image to accept the following command but
> _/subsystem=modcluster/mod-cluster-config=configuration:write-attribute(name=proxies,value=[${modcluster.host:modcluster}:${modcluster.port:80}])_
> but if fails with:{color:red} "Services that may be the cause:" => ["jboss.outbound-socket-binding.\"${modcluster.host:modcluster}:${modcluster.port:80}\""]{color}
> With /subsystem=modcluster/:add-proxy(host=${modcluster.host:modcluster},port=80) it fails with WFLYMODCLS0016: No IP address could be resolved for the specified host of the proxy.



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