1 2 Previous Next 16 Replies Latest reply on Dec 23, 2013 3:10 AM by isa154

    mod_cluster and wildfly8 can't identify port-offset

    sndaemon

      HI,

      I'm trying to setup a combination of mod_cluster-1.2.0.Final,wildfly-8.0.0.Alpha4 on Red Hat Enterprise Linux Server release 5.5 (Tikanga) ,but it seems like the new subsystem undertow1.0 can't identify port-offset.

       

      Versions of my softwares as follows:

      wildfly-8.0.0.Alpha4.tar.gz

      jdk-7u25-linux-i586.rpm

      mod_cluster-1.2.0.Final-linux2-x64-ssl.tar.gz

       

      I installed wildfly8 and mod_cluster  reference steps of https://docs.jboss.org/author/display/AS72/AS7+Cluster+Howto

      The cluster contains four servers,start up with domain mode:

      10.19.222.52:server1/server2

      10.19.222.53:server3/server4

      10.19.222.50:apache

       

      The config files as attached:

       

       

      Search errorlog of Apache ,the proxy:AJP always acquired connection through initial AJP port(8009) define in domain.xml.

      The port-offset is 100 ,why it didn't detect the other port(8109) to server2 and server4?

      Any mistake i have made in the process?

       

      [Fri Sep 13 21:07:40 2013] [debug] mod_proxy_cluster.c(773): ajp_cping_cpong: Done

      [Fri Sep 13 21:07:40 2013] [debug] proxy_util.c(2029): proxy: ajp: has released connection for (10.19.222.52)

      [Fri Sep 13 21:07:43 2013] [debug] proxy_util.c(2011): proxy: ajp: has acquired connection for (10.19.222.53)

      [Fri Sep 13 21:07:43 2013] [debug] proxy_util.c(2067): proxy: connecting ajp://10.19.222.53:8009/ to 10.19.222.53:8009

      [Fri Sep 13 21:07:43 2013] [debug] proxy_util.c(2193): proxy: connected ajp://10.19.222.53:8009/ to 10.19.222.53:8009

      [Fri Sep 13 21:07:43 2013] [debug] mod_proxy_cluster.c(773): ajp_cping_cpong: Done

      [Fri Sep 13 21:07:43 2013] [debug] proxy_util.c(2029): proxy: ajp: has released connection for (10.19.222.53)

      [Fri Sep 13 21:07:45 2013] [debug] proxy_util.c(2011): proxy: ajp: has acquired connection for (10.19.222.52)

      [Fri Sep 13 21:07:45 2013] [debug] proxy_util.c(2067): proxy: connecting ajp://10.19.222.52:8009/ to 10.19.222.52:8009

      [Fri Sep 13 21:07:45 2013] [debug] proxy_util.c(2193): proxy: connected ajp://10.19.222.52:8009/ to 10.19.222.52:8009

      [Fri Sep 13 21:07:45 2013] [debug] mod_proxy_cluster.c(773): ajp_cping_cpong: Done

      [Fri Sep 13 21:07:45 2013] [debug] proxy_util.c(2029): proxy: ajp: has released connection for (10.19.222.52)

      [Fri Sep 13 21:07:46 2013] [debug] mod_manager.c(1667): manager_trans STATUS (/)

      [Fri Sep 13 21:07:46 2013] [debug] mod_manager.c(2323): manager_handler STATUS (/) processing: "JVMRoute=2644d861-0ead-352c-ba1e-619f1e1f25e8&Load=100"

      [Fri Sep 13 21:07:46 2013] [debug] mod_manager.c(1404): Processing STATUS

      [Fri Sep 13 21:07:46 2013] [debug] proxy_util.c(2011): proxy: ajp: has acquired connection for (10.19.222.53)

      [Fri Sep 13 21:07:46 2013] [debug] proxy_util.c(2067): proxy: connecting ajp://10.19.222.53:8009/ to 10.19.222.53:8009

      [Fri Sep 13 21:07:46 2013] [debug] proxy_util.c(2193): proxy: connected ajp://10.19.222.53:8009/ to 10.19.222.53:8009

      [Fri Sep 13 21:07:46 2013] [debug] mod_proxy_cluster.c(773): ajp_cping_cpong: Done

      [Fri Sep 13 21:07:46 2013] [debug] proxy_util.c(2029): proxy: ajp: has released connection for (10.19.222.53)

      [Fri Sep 13 21:07:46 2013] [debug] mod_manager.c(2366): manager_handler STATUS  OK

      [Fri Sep 13 21:07:47 2013] [debug] mod_manager.c(1667): manager_trans STATUS (/)

      [Fri Sep 13 21:07:47 2013] [debug] mod_manager.c(2323): manager_handler STATUS (/) processing: "JVMRoute=ea81701b-f847-34a8-9534-0ac5c489af90&Load=100"

      [Fri Sep 13 21:07:47 2013] [debug] mod_manager.c(1404): Processing STATUS

      [Fri Sep 13 21:07:47 2013] [debug] proxy_util.c(2011): proxy: ajp: has acquired connection for (10.19.222.52)

      [Fri Sep 13 21:07:47 2013] [debug] proxy_util.c(2067): proxy: connecting ajp://10.19.222.52:8009/ to 10.19.222.52:8009

      [Fri Sep 13 21:07:47 2013] [debug] proxy_util.c(2193): proxy: connected ajp://10.19.222.52:8009/ to 10.19.222.52:8009



       

       

      Please help,thanks!

       

       

       


        • 1. Re: mod_cluster and wildfly8 can't identify port-offset
          wujiee

          @Stuart Douglas  @Jean-Frederic Clere

          Could you help us to solve the problem? Any suggestions or comments was appreciated.


          Thanks!

          • 2. Re: mod_cluster and wildfly8 can't identify port-offset
            jfclere

            I think you don't use the right socket-binding...  you need port-offset in the binding.

            That is not a mod_cluster problem just WF8 configuration issue.

            • 3. Re: mod_cluster and wildfly8 can't identify port-offset
              sndaemon

              Sorry,I don't know what's the problem with my configuration.

              Whether or not i added port-offset in the socket-binding-group:

              it still could't indentify the port 8109.

              Just like AS7,i think it can detect all the ajp ports automatically without adding the port-offset in the binding.

              Because i have added port-offset in the code blocks of  servers:

              In fact,it still can't work.

              @Stuart Douglas  @Jean-Frederic Clere

              • 4. Re: mod_cluster and wildfly8 can't identify port-offset
                jaikiran

                This thread has been marked as "Assumed Answered". Was this really solved?

                • 5. Re: mod_cluster and wildfly8 can't identify port-offset
                  sndaemon

                  Sorry,this problem is still bothering me.

                  I am waiting for result from [#WFLY-2125] wildfly8 can't identify port-offset - JBoss Issue Tracker.

                  • 6. Re: mod_cluster and wildfly8 can't identify port-offset
                    ctomc

                    This should be fixed now.

                     

                    Fix is now in latest master and will be part of upcoming Beta1 release.

                    • 7. Re: mod_cluster and wildfly8 can't identify port-offset
                      sndaemon

                      OK,thanks.

                      I'm looking forward to the new release.

                      • 8. Re: Re: mod_cluster and wildfly8 can't identify port-offset
                        sndaemon

                        Tomaz Cerar

                        jfclere

                        jaikiran

                        Hi,I'm sorry,it seems that the problem is still not been resolved though the new version has been released.

                        I used the 8.0.0.Beta1,but the problem is still exist.

                        • 9. Re: Re: mod_cluster and wildfly8 can't identify port-offset
                          ctomc

                          What kind of problem is it now?

                           

                          It doubt it is same problem with port-offset not working.

                           

                          what do logs say?

                          • 10. Re: mod_cluster and wildfly8 can't identify port-offset
                            sndaemon

                            The same as before:

                             

                            [Wed Oct 09 16:03:39 2013] [debug] proxy_util.c(2193): proxy: connected ajp://10.19.222.53:8009/ to 10.19.222.53:8009

                            [Wed Oct 09 16:03:39 2013] [debug] proxy_util.c(2444): proxy: ajp: fam 2 socket created to connect to 10.19.222.53

                            [Wed Oct 09 16:03:39 2013] [debug] mod_proxy_cluster.c(773): ajp_cping_cpong: Done

                            [Wed Oct 09 16:03:39 2013] [debug] proxy_util.c(2029): proxy: ajp: has released connection for (10.19.222.53)

                            [Wed Oct 09 16:03:39 2013] [debug] mod_manager.c(2366): manager_handler STATUS  OK

                            [Wed Oct 09 16:03:39 2013] [debug] mod_proxy_cluster.c(678): update_workers_node starting

                            [Wed Oct 09 16:03:39 2013] [debug] mod_proxy_cluster.c(693): update_workers_node done

                            [Wed Oct 09 16:03:39 2013] [debug] proxy_util.c(2011): proxy: ajp: has acquired connection for (10.19.222.53)

                            [Wed Oct 09 16:03:39 2013] [debug] proxy_util.c(2067): proxy: connecting ajp://10.19.222.53:8009/ to 10.19.222.53:8009

                            [Wed Oct 09 16:03:39 2013] [debug] proxy_util.c(2193): proxy: connected ajp://10.19.222.53:8009/ to 10.19.222.53:8009

                            [Wed Oct 09 16:03:39 2013] [debug] mod_proxy_cluster.c(773): ajp_cping_cpong: Done

                            [Wed Oct 09 16:03:39 2013] [debug] proxy_util.c(2029): proxy: ajp: has released connection for (10.19.222.53)

                            [Wed Oct 09 16:03:39 2013] [debug] mod_proxy_cluster.c(678): update_workers_node starting

                            [Wed Oct 09 16:03:39 2013] [debug] mod_proxy_cluster.c(693): update_workers_node done

                            [Wed Oct 09 16:03:39 2013] [debug] mod_proxy_cluster.c(678): update_workers_node starting

                            [Wed Oct 09 16:03:39 2013] [debug] mod_proxy_cluster.c(258): Created: reusing worker for ajp://10.19.222.53:8009

                            [Wed Oct 09 16:03:39 2013] [debug] mod_proxy_cluster.c(360): proxy: initialized worker 1 in child 5998 for (10.19.222.53) min=0 max=25 smax=25

                            [Wed Oct 09 16:03:39 2013] [debug] mod_proxy_cluster.c(418): Created: worker for ajp://10.19.222.53:8009 1 (status): 1

                            [Wed Oct 09 16:03:39 2013] [debug] mod_proxy_cluster.c(693): update_workers_node done

                            [Wed Oct 09 16:03:39 2013] [debug] mod_proxy_cluster.c(678): update_workers_node starting

                            [Wed Oct 09 16:03:39 2013] [debug] mod_proxy_cluster.c(693): update_workers_node done

                            [Wed Oct 09 16:03:40 2013] [debug] mod_manager.c(1667): manager_trans STATUS

                            [Wed Oct 09 16:03:40 2013] [debug] mod_manager.c(2323): manager_handler STATUS processing: "JVMRoute=ea81701b-f847-34a8-9534-0ac5c489af90&Load=100"

                            [Wed Oct 09 16:03:40 2013] [debug] mod_manager.c(1404): Processing STATUS

                            [Wed Oct 09 16:03:40 2013] [debug] proxy_util.c(2011): proxy: ajp: has acquired connection for (10.19.222.52)

                            [Wed Oct 09 16:03:40 2013] [debug] proxy_util.c(2067): proxy: connecting ajp://10.19.222.52:8009/ to 10.19.222.52:8009

                            [Wed Oct 09 16:03:40 2013] [debug] proxy_util.c(2193): proxy: connected ajp://10.19.222.52:8009/ to 10.19.222.52:8009

                            [Wed Oct 09 16:03:40 2013] [debug] mod_proxy_cluster.c(773): ajp_cping_cpong: Done [Wed Oct 09 16:03:40 2013] [debug] proxy_util.c(2029): proxy: ajp: has released connection for (10.19.222.52)

                            [Wed Oct 09 16:03:40 2013] [debug] mod_manager.c(2366): manager_handler STATUS  OK

                            [Wed Oct 09 16:03:41 2013] [debug] mod_manager.c(1667): manager_trans INFO

                            [Wed Oct 09 16:03:41 2013] [debug] mod_manager.c(2323): manager_handler INFO processing: ""

                            [Wed Oct 09 16:03:41 2013] [debug] mod_manager.c(2366): manager_handler INFO  OK

                            [Wed Oct 09 16:03:41 2013] [debug] mod_manager.c(1667): manager_trans CONFIG

                            [Wed Oct 09 16:03:41 2013] [debug] mod_manager.c(2323): manager_handler CONFIG processing: "JVMRoute=2644d861-0ead-352c-ba1e-619f1e1f25e8&Host=10.19.222.53&Maxattempts=1&Port=8009&Reversed=true&StickySessionForce=No&Type=ajp&ping=10"

                            [Wed Oct 09 16:03:41 2013] [debug] mod_manager.c(2366): manager_handler CONFIG  OK

                            [Wed Oct 09 16:03:41 2013] [debug] mod_manager.c(1667): manager_trans STATUS

                            [Wed Oct 09 16:03:41 2013] [debug] mod_manager.c(2323): manager_handler STATUS processing: "JVMRoute=2644d861-0ead-352c-ba1e-619f1e1f25e8&Load=100"

                            [Wed Oct 09 16:03:41 2013] [debug] mod_manager.c(1404): Processing STATUS

                             

                            The port_offset of server-two is 150.

                            Apache log shows it can't detect 8159.

                            Wildfly is normal,it has no error logs and Undertow AJP listener ajp has already listened on the port 8159.

                             

                            [Server:server-two] 20:11:35,674 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-13) JBAS017519: Undertow AJP listener ajp listening on /10.19.222.52:8159

                            [Server:server-two] 20:11:35,688 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-10) JBAS017519: Undertow HTTP listener default listening on /10.19.222.52:8230

                            • 11. Re: mod_cluster and wildfly8 can't identify port-offset
                              rhusar

                              I will take a look.

                              • 12. Re: mod_cluster and wildfly8 can't identify port-offset
                                rhusar

                                So clearly the problem is that the listener is correctly listening on the shifted port:

                                 

                                [Server:server-two] 20:11:35,674 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-13) JBAS017519: Undertow AJP listener ajp listening on /10.19.222.52:8159

                                but the offet is not picked up by the LB:

                                 

                                [Wed Oct 09 16:03:40 2013] [debug] proxy_util.c(2193): proxy: connected ajp://10.19.222.52:8009/ to 10.19.222.52:8009

                                 

                                Looks like a bug. Looking into it.

                                • 13. Re: mod_cluster and wildfly8 can't identify port-offset
                                  isa154

                                  I having the same issue the LB is not pciking up the off-set

                                  1 2 Previous Next