3 Replies Latest reply on Nov 15, 2013 9:35 AM by rhusar

    mod_cluster in front of a DMZ

    mylos78

      Hi all!

      We are planning a migration from mod_jk to mod_cluster for our JBoss 7 applications. We have the following scenario: Apache in front of the application servers which are part of a DMZ. Since Apache and the application servers will not be in the same network (e.g. 192.168.XX Apache 192.168.YY JBoss). In this scenario I guess it is not possible to communicate using multicast messages right ? my only choice is to use the proxy-list attribute and enter the static IP address ?

      Thanks

      Mylos

        • 1. Re: mod_cluster in front of a DMZ
          belaban

          That's recommended, yes. The proxy-list should include all httpd daemons.

          • 2. Re: mod_cluster in front of a DMZ
            mylos78

            Thanks Bela!

            • 3. Re: mod_cluster in front of a DMZ
              rhusar

              That's right, let me just add you can still add new balancers on-the-fly via CLI:

               

              [standalone@localhost:9999 /] /subsystem=modcluster:add-proxy(host=localhost, port=6666)

              {"outcome" => "success"}

              [standalone@localhost:9999 /] /subsystem=modcluster/mod-cluster-config=configuration/:write-attribute(name=proxy-list, value="localhost:6666")

              {

                  "outcome" => "success",

                  "response-headers" => {

                      "operation-requires-reload" => true,

                      "process-state" => "reload-required"

                  }

              }

               

              So no need to change static configuration like one has to do for mod_jk.