Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-5840

mod_cluster proxies doesn't accept expressions

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • 9.0.2.Final
    • Clustering

      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.

              rhn-engineering-rhusar Radoslav Husar
              rafabene_jira Rafael Benevides (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: