2 Replies Latest reply on Jun 6, 2016 9:48 PM by Anton Sar

    Service unavailable right after mod_cluster registered apps, fixed random ajp port.  Mod Cluster 1.3.1, Httpd 2.4.6, Tomcat 8

    Anton Sar Newbie

      Hello,


      Please help me with this issue, I am quite new with apache/mod cluster and really need this to work.  I already spent days on this, and deadline is approaching


      The issue I observed is explained in greater details below (in "Issue observed" section), the symtomps is the same as was described on the following links:

      https://developer.jboss.org/thread/262017?start=0&tstart=0

      https://developer.jboss.org/thread/252841?start=0&tstart=0

      https://developer.jboss.org/message/923228#923228


      Based off the links above it seems the issue maybe stems from Mod Cluster interacting with outside elements. Though I really hope the real issue would be something silly from my end.


      My setup is as follow:

      -Mod Cluster 1.3.1 Final

      -Apache 2.4.6 (httpd) (installed using yum, as explained here http://unix.stackexchange.com/questions/138899/centos-install-using-yum-apache-2-4)

      -Tomcat 8.0.12 -CentOS 6.5


      Background on System:

      -This is a VM, with internet connection

      -SELinux is set to permissive (setenforce 0), issue remains so later on I set it to disabled in /etc/selinux/config

      -Firewall is stopped (ran service iptables stop, service ip6tables stop)

      -There is No DNS


      Background on Setup:

      -Everything is in this 1 VM

      -Tomcat has several apps deployed


      Issue observed:

      -With httpd started and Tomcat off, I could access the test home page http://127.0.0.1:80/ and the http://127.0.0.1:6666/mod_cluster_manager pages

      -Once Tomcat is started after a bit (just a minute or two), the mod_cluster_manager web page shows all the application deployed in Tomcat with Status: NOTOK.  Hitting the apps, logging in etc the Request count remains at 0 Below is what it looks like on the http://127.0.0.1:6666/mod_cluster_manager 


      mod_cluster/1.3.1.Final Auto Refresh show DUMP output show INFO output Node jvm1 (ajp://127.0.0.1:8009):

      Enable Contexts Disable Contexts Stop Contexts Balancer: mycluster,LBGroup: ,Flushpackets: Off,Flushwait: 10000,Ping: 10000000,Smax: 2,Ttl: 60000000,Status: NOTOK,Elected: 0,Read: 0,Transferred: 0,Connected: 0,Load: -1


      Virtual Host 1:

      Contexts:

      /app1, Status: ENABLED Request: 0 Disable Stop

      /, Status: ENABLED Request: 0 Disable Stop

      /examples, Status: ENABLED Request: 0 Disable Stop

      /app2, Status: ENABLED Request: 0 Disable Stop

      /host-manager, Status: ENABLED Request: 0 Disable Stop

      /manager, Status: ENABLED Request: 0 Disable Stop

      /docs, Status: ENABLED Request: 0 Disable Stop


      Aliases: localhost


      -When the mod_cluster_manager web app looks like the above, the home page http://127.0.0.1:80/ shows the following:

      Service Unavailable

      The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

       


      Note*: app name in the logs are modified from their original name to app1 and app2, nothing else. - the usual corporate rules