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

[Radoslav Husar (JIRA)]

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

Radoslav Husar edited comment on WFLY-5840 at 12/13/15 7:46 PM:
----------------------------------------------------------------

To understand an attribute, its best to read the description:

{noformat}
[standalone at localhost:9990 /] /subsystem=modcluster/mod-cluster-config=configuration/:read-resource-description
{
    "outcome" => "success",
    "result" => {
...
                "description" => "List of proxies for mod_cluster to register with defined by outbound-socket-binding in socket-binding-group.",
{noformat}

What you want to use is this, run in a batch ideally:

{noformat}
[standalone at localhost:9990 /] /subsystem=modcluster/mod-cluster-config=configuration/:write-attribute(name=advertise,value=false
{
    "outcome" => "success",
    "response-headers" => {
        "operation-requires-reload" => true,
        "process-state" => "reload-required"
    }
}
[standalone at localhost:9990 /] /subsystem=modcluster/mod-cluster-config=configuration/:write-attribute(name=proxies,value=[proxy1]
{
    "outcome" => "success",
    "response-headers" => {
        "operation-requires-reload" => true,
        "process-state" => "reload-required"
    }
}
[standalone at localhost:9990 /] /socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=proxy1:add(host=${modcluster.host:modcluster},port=${modcluster.port:80}
{
    "outcome" => "success",
    "response-headers" => {"process-state" => "reload-required"}
}
[standalone at localhost:9990 /] :reload
{
    "outcome" => "success",
    "result" => undefined
}
{noformat}




was (Author: rhusar):
To understand an attribute, its best to read the description:

{noformat}
[standalone at localhost:9990 /] /subsystem=modcluster/mod-cluster-config=configuration/:read-resource-description
{
    "outcome" => "success",
    "result" => {
...
                "description" => "List of proxies for mod_cluster to register with defined by outbound-socket-binding in socket-binding-group.",
{noformat}

> 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: Radoslav Husar
>              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
> {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}



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