proxy-list attribute in moccluster subsystem does not work correctly

Solution Unverified - Updated

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 7.3

Issue

When proxy-list attribute in modcluster subsystem is set for connecting Apache and JBoss by static IP address list, the JBoss instance doesn't show up in Apache's /mod_cluster_manager node list. Is proxy-list read as a valid attribute?

<subsystem xmlns="urn:jboss:domain:modcluster:5.0">
    <proxy name="default" advertise="false" advertise-socket="modcluster" listener="ajp" proxy-list="127.0.0.1:6666">
        <dynamic-load-provider>
            <load-metric type="cpu"/>
        </dynamic-load-provider>
    </proxy>
</subsystem>

Resolution

This is a known issue This content is not included.JBEAP-20377. JBoss EAP7.3.z cannot load the proxy-list correctly due to this issue. proxy-list attribute has been replaced by proxies since EAP7 and marked as deprecated, however, proxy-list should be available for backward compatibility.

As a workaround, setting proxies attribute as described in Congiruation Guide 24.6.2. Disable Advertising for mod_cluster instead of proxy-list:

$ diff -u standalone-ha.xml.original standalone-ha.xml
--- standalone-ha.xml.original	2020-10-21 15:22:41.828489646 +0900
+++ standalone-ha.xml	2020-10-21 15:23:29.843072774 +0900
@@ -461,7 +461,7 @@
         <subsystem xmlns="urn:wildfly:microprofile-metrics-smallrye:2.0" security-enabled="false" exposed-subsystems="*" prefix="${wildfly.metrics.prefix:jboss}"/>
         <subsystem xmlns="urn:wildfly:microprofile-opentracing-smallrye:1.0"/>
         <subsystem xmlns="urn:jboss:domain:modcluster:5.0">
-            <proxy name="default" advertise-socket="modcluster" listener="ajp">
+            <proxy name="default" advertise="false" advertise-socket="modcluster" listener="ajp" proxies="apache-modcluster">
                 <dynamic-load-provider>
                     <load-metric type="cpu"/>
                 </dynamic-load-provider>
@@ -589,6 +589,9 @@
         <socket-binding name="modcluster" multicast-address="${jboss.modcluster.multicast.address:224.0.1.105}" multicast-port="23364"/>
         <socket-binding name="txn-recovery-environment" port="4712"/>
         <socket-binding name="txn-status-manager" port="4713"/>
+        <outbound-socket-binding name="apache-modcluster">
+            <remote-destination host="127.0.0.1" port="6666"/>
+        </outbound-socket-binding>
         <outbound-socket-binding name="mail-smtp">
             <remote-destination host="localhost" port="25"/>
         </outbound-socket-binding>
SBR
Product(s)
Components
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.