CLOUD-3506 Remove mod_cluster from OpenShift default configuration

Author: rhusar

jboss/container/config/cd/19.0/standalone-openshift.xml

@@ -15,7 +15,6 @@
         <extension module="org.jboss.as.jsf"/>
         <extension module="org.jboss.as.logging"/>
         <extension module="org.jboss.as.mail"/>
-        <extension module="org.jboss.as.modcluster"/>
         <extension module="org.jboss.as.naming"/>
         <extension module="org.jboss.as.pojo"/>
         <extension module="org.jboss.as.remoting"/>
@@ -460,13 +459,6 @@
         <subsystem xmlns="urn:wildfly:microprofile-health-smallrye:2.0" security-enabled="false" empty-liveness-checks-status="${env.MP_HEALTH_EMPTY_LIVENESS_CHECKS_STATUS:UP}" empty-readiness-checks-status="${env.MP_HEALTH_EMPTY_READINESS_CHECKS_STATUS:UP}"/>
         <subsystem xmlns="urn:wildfly:microprofile-jwt-smallrye:1.0"/>
         <subsystem xmlns="urn:wildfly:microprofile-metrics-smallrye:2.0" security-enabled="false" exposed-subsystems="*" prefix="${wildfly.metrics.prefix:jboss}"/>
-        <subsystem xmlns="urn:jboss:domain:modcluster:5.0">
-            <proxy name="default" advertise-socket="modcluster" listener="ajp">
-                <dynamic-load-provider>
-                    <load-metric type="cpu"/>
-                </dynamic-load-provider>
-            </proxy>
-        </subsystem>
         <subsystem xmlns="urn:jboss:domain:naming:2.0">
             <remote-naming/>
         </subsystem>
@@ -579,7 +571,6 @@
         <socket-binding name="jgroups-udp" interface="private" port="55200" multicast-address="${jboss.default.multicast.address:230.0.0.4}" multicast-port="45688"/>
         <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>
         <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9993}"/>
-        <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="http-messaging">

jboss/container/eap/galleon/config/ee/artifacts/opt/jboss/container/eap/galleon/eap-s2i-galleon-pack/src/main/resources/configs/standalone/standalone.xml/config.xml

@@ -4,7 +4,7 @@
     <layers>
         <!-- we already have all required in default config -->
         <!-- Although logically correct, galleon doesn't actually support excluding from model -->
-        <!-- This is harmeless, keeping the exclusion commented for reference until GAL-308 is fixed -->
+        <!-- This is harmless, keeping the exclusion commented for reference until GAL-308 is fixed -->
         <!--<exclude name="operator-required"/>-->
         <include name="amq6-rar"/>
     </layers>
@@ -17,21 +17,6 @@
     <exclude feature-id="core-service.management.security-realm.server-identity.ssl:security-realm=ApplicationRealm"/>
     <feature-group name="os-management"/>
 
-    <!-- mod-cluster -->
-    <!-- required by modcluster -->
-    <feature spec="subsystem.undertow">
-        <feature spec="subsystem.undertow.server">
-            <param name="server" value="default-server"/>
-            <feature spec="subsystem.undertow.server.ajp-listener">
-                <param name="ajp-listener" value="ajp"/>
-                <param name="socket-binding" value="ajp"/>
-                <unset param="worker"/>
-                <unset param="buffer-pool"/>
-            </feature>
-        </feature>
-    </feature>
-    <feature-group name="modcluster"/>
-
     <!-- messaging -->
     <feature spec="subsystem.messaging-activemq"/>
     <feature-group name="os-messaging"/>