1 Reply Latest reply on Jun 24, 2014 8:29 AM by Radoslav Husar

    MOD_Cluster  in standalone error

    ismael Cad Newbie


      I use mod_cluster 1.26, 2 server jboss AS 7.1.1 (nodeA and NodeB).

      In both file standalone i add :


      <subsystem xmlns="urn:jboss:domain:modcluster:1.0">

                  <mod-cluster-config advertise-socket="modcluster" proxy-list="">


                          <load-metric type="busyness"/>





      and this is my httpdconf:




      LoadModule proxy_module modules/mod_proxy.so

      LoadModule proxy_ajp_module modules/mod_proxy_ajp.so

      LoadModule proxy_http_module modules/mod_proxy_http.so

      LoadModule proxy_cluster_module modules/mod_proxy_cluster.so

      LoadModule manager_module modules/mod_manager.so

      LoadModule slotmem_module modules/mod_slotmem.so

      LoadModule advertise_module modules/mod_advertise.so




      # Adjust to you hostname and subnet.

      <IfModule manager_module>


        ManagerBalancerName mycluster


          <Location />

           Order deny,allow

           Deny from all

           Allow from




          KeepAliveTimeout 300

          MaxKeepAliveRequests 0

          #ServerAdvertise on

          AdvertiseFrequency 5

          #AdvertiseSecurityKey secret





          <Location /mod_cluster_manager>

             SetHandler mod_cluster-manager

             Order deny,allow

             Deny from all

             Allow from 127.0.0







      when i  start my both jboss serveur :

      07:04:39,064 ERROR [org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Error [null: null: {4}] sending command INFO to proxy, configuration will be reset


      and acces to mod_cluster proxy its work but not work.


      If i put in only one file proxy-list="", i can acces to in only one node !


      Have you ideas to help me ?