Uploaded image for project: 'mod_cluster'
  1. mod_cluster
  2. MODCLUSTER-794

mod_proxy_cluster gets stuck with 20 nodes

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • native-2.0.0.Beta1
    • None
    • None
    • None
    • Hide

      (given you have tomcat container image and the test config):

      • run httpd with mod_proxy_cluster
      • execute
        • for i in {1..20}; do docker run -d --network=host -e tomcat_ajp_port=8010 -e tomcat_address=127.0.0.$i -e tomcat_shutdown_port=8005 -e jvm_route=tomcat$i --name tomcat$i tomcat-image; done
      • once nodes all running it stops responding: check http://localhost:6666 or http://localhost:6666/mod_cluster_manager
      Show
      (given you have tomcat container image and the test config): run httpd with mod_proxy_cluster execute for i in {1..20}; do docker run -d --network=host -e tomcat_ajp_port=8010 -e tomcat_address=127.0.0.$i -e tomcat_shutdown_port=8005 -e jv m_route=tomcat$i --name tomcat$i tomcat-image; done once nodes all running it stops responding: check http://localhost:6666 or http://localhost:6666/mod_cluster_manager
    • Hide

      The workaround was incorrect. There is now an open PR on GitHub.

      Show
      The workaround was incorrect. There is now an open PR on GitHub.

      httpd with the mod_proxy_cluster 2.x gets stuck in case 20 tomcat nodes connect to it. Logs are full of: file mod_proxy_cluster.c, line 363, assertion "0" failed

       

      Note: The Maxnode property is by default 20.

              vchlup@redhat.com Vladimir Chlup
              vchlup@redhat.com Vladimir Chlup
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: