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

[ https://issues.jboss.org/browse/WFLY-5840?page=com.atlassian.jira.plugin.... ] 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 {noformat} /subsystem=modcluster/mod-cluster-config=configuration:write-attribute(name=proxies,value=[${modcluster.host:modcluster}:${modcluster.port:80}])}} {noformat} but if fails with:{color:red} "Services that may be the cause:" => ["jboss.outbound-socket-binding.\"${modcluster.host:modcluster}:${modcluster.port:80}\""]{color} With {noformat} /subsystem=modcluster/:add-proxy(host=${modcluster.host:modcluster},port=80) {noformat} it fails with {color:red}WFLYMODCLS0016: No IP address could be resolved for the specified host of the proxy.{color} 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 {noformat} /subsystem=modcluster/mod-cluster-config=configuration:write-attribute(name=proxies,value=[${modcluster.host:modcluster}:${modcluster.port:80}])}} {noformat} 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)