4 Replies Latest reply on Apr 29, 2014 5:45 PM by Mustaq Pradhan

    load-balancer cannot access application because mod_cluster cannot find node

    Mustaq Pradhan Newbie

      We are running a multi-host domain of JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) on Red Hat Enterprise Linux Server release 6.5.

       

      We have following modules:

       

      mod_cluster-native-1.2.4-1.Final.redhat_1.ep6.el6.x86_64

      mod_cluster-1.2.4-1.Final_redhat_1.ep6.el6.noarch

      jboss-as-modcluster-7.2.0-8.Final_redhat_8.ep6.el6.noarch

       

      The mod_cluster.conf is:

      LoadModule slotmem_module  modules/mod_slotmem.so

      LoadModule proxy_cluster_module modules/mod_proxy_cluster.so

      LoadModule advertise_modulemodules/mod_advertise.so
      LoadModule manager_module  modules/mod_manager.so

       

      <Location /mod_cluster_manager>

      SetHandler mod_cluster-manager

      </Location>

       

      Listen ut-j10-01.appu.test.det.nsw.edu.au:10001

      <VirtualHost ut-j10-01.appu.test.det.nsw.edu.au:10001>

         KeepAliveTimeout 60

         MaxKeepAliveRequests 0

         ManagerBalancerName mycluster

       

         ServerAdvertise On

         AdvertiseFrequency 5

         AdvertiseGroup 228.1.10.1:23364

       

         EnableMCPMReceive

       

      </VirtualHost>

       

      AllowCmd Off

       

      Maxhost 1000

      Maxnode 100

       

      We are getting following errors on the server.log

       

      24-04-2014 10:19:14.394 +1000 ERROR [org.jboss.modcluster] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) MODCLUSTER000042: Error MEM sending STATUS command to ut-j10-03.appu.test.det.nsw.edu.au/153.107.90.149:10001, configuration will be reset: MEM: Can't read node

      24-04-2014 10:19:14.396 +1000 ERROR [org.jboss.modcluster] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) MODCLUSTER000042: Error MEM sending STATUS command to ut-j10-01.appu.test.det.nsw.edu.au/153.107.90.147:10001, configuration will be reset: MEM: Can't read node

      24-04-2014 10:24:34.666 +1000 ERROR [org.jboss.modcluster] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) MODCLUSTER000042: Error MEM sending STATUS command to ut-j10-02.appu.test.det.nsw.edu.au/153.107.90.148:10001, configuration will be reset: MEM: Can't read node

      24-04-2014 10:24:44.679 +1000 ERROR [org.jboss.modcluster] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) MODCLUSTER000042: Error MEM sending STATUS command to ut-j10-03.appu.test.det.nsw.edu.au/153.107.90.149:10001, configuration will be reset: MEM: Can't read node

      24-04-2014 10:24:44.681 +1000 ERROR [org.jboss.modcluster] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) MODCLUSTER000042: Error MEM sending STATUS command to ut-j10-01.appu.test.det.nsw.edu.au/153.107.90.147:10001, configuration will be reset: MEM: Can't read node

       

      Also warnings on the apache error.log

       

      [Thu Apr 24 10:24:44 2014] [warn] manager_handler STATUS error: MEM: Can't read node

       

      The web & modcluster subsystems are configured as:

       

                  <subsystem xmlns="urn:jboss:domain:web:1.4" default-virtual-server="default-host" instance-id="${jboss.node.name}" native="false">

                      <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http"/>

                      <connector name="ajp" protocol="AJP/1.3" scheme="https" socket-binding="ajp" proxy-port="443" secure="true"/>

                      <virtual-server name="default-host" enable-welcome-root="true">

                          <alias name="localhost"/>

                          <alias name="example.com"/>

                      </virtual-server>

                  </subsystem>

       

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

                      <mod-cluster-config advertise-socket="modcluster" balancer="mycluster" load-balancing-group="mycluster" connector="ajp">

                          <dynamic-load-provider>

                              <load-metric type="busyness"/>

                          </dynamic-load-provider>

                      </mod-cluster-config>

                  </subsystem>

       

      When I am getting this error,  I can access application directly going to the server's apache on the port (eg., http://ud-j10-03.appu.dev.det.nsw.edu.au/smu/)

      But I cannot access from the load-balancer url.

       

      Is there any way to fix this?

      Is it possible to get the application without restarting the server? I have tried restating httpd, didn't help.

       

      Thanks for your help.