4 Replies Latest reply on Mar 11, 2015 10:11 AM by Rob Alelyunas

    mod cluster with apache 2.4 and 1.3.1 Beta2

    Rob Alelyunas Newbie

      I had a working mod cluster installation with JBoss AS 7.2 and upgraded to apache 2.4.  I downloaded mod cluster 1.3.1 Beta2 binaries, its for ubuntu 64, and installed the shared libraries in the /usr/lib/apache2/modules folder.  I had to modify the file /etc/apache2/mods_available/mod_cluster.load so it looks like this:


      LoadModule proxy_module /usr/lib/apache2/modules/mod_proxy.so

      LoadModule proxy_http_module /usr/lib/apache2/modules/mod_proxy_http.so

      LoadModule proxy_ajp_module /usr/lib/apache2/modules/mod_proxy_ajp.so

      LoadModule cluster_slotmem_module /usr/lib/apache2/modules/mod_cluster_slotmem.so

      LoadModule manager_module /usr/lib/apache2/modules/mod_manager.so

      LoadModule proxy_cluster_module /usr/lib/apache2/modules/mod_proxy_cluster.so

      LoadModule advertise_module /usr/lib/apache2/modules/mod_advertise.so


      When I run the JBoss instance and start apache, I get this in the JBoss log:


      20:16:59,606 ERROR [org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Error [MEM: MEM: Can't read node: {4}] sending command STATUS to proxy localhost/, configuration will be reset


      And this in the error.log for apache:


      [Sun Mar 08 20:18:09.620074 2015] [proxy:error] [pid 20770:tid 140360904746752] (111)Connection refused: AH00957: ajp: attempt to connect to ( failed

      [Sun Mar 08 20:18:09.620150 2015] [proxy:error] [pid 20770:tid 140360904746752] AH00959: ap_proxy_connect_backend disabling worker for ( for 60s

      [Sun Mar 08 20:18:09.716750 2015] [proxy:error] [pid 20770:tid 140360921532160] AH00940: ajp: disabled connection for (

      [Sun Mar 08 20:18:14.717485 2015] [proxy:error] [pid 20770:tid 140360921532160] AH00940: ajp: disabled connection for (


      I inherited all this setup so I'm not that clued in on how mod_cluster works, but I am guessing the JBoss tells the mod_cluster on port 6666 about its status, and then mod_cluster does load balancing including that node. But where is it getting the port "11831"  there is nothing running on that port.  Obviously connection refused, there is nothing running on that port.  In standalone.xml I see this:


      <socket-binding name="ajp" port="8009"/>

      I think that should mean the ajp port is 8009. 

      Any hints?  Anybody can explain how this works a little better?