8 Replies Latest reply on Jun 8, 2004 1:02 PM by Holger Baxmann

    3.2.4 cluster testsuite

    Holger Baxmann Novice

      The testsuite does not run through on a multihomed system, there are some:

      Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectE
      xception: Connection refused: connect]
      at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:190)
      ... 45 more

      so the "-b" parameter is ingored here too.

      bax

        • 1. Re: 3.2.4 cluster testsuite
          Scott Stark Master

          Provide more info as the listening port address bindings look fine with the exception of the snmp adaptor which currently does not support this:

          [starksm@lamia starksm]$ netstat -an
          Active Internet connections (servers and established)
          Proto Recv-Q Send-Q Local Address Foreign Address State
          tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
          tcp 0 0 0.0.0.0:23 0.0.0.0:* LISTEN
          tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN
          
          run.sh -c all -b 172.17.66.55
          [starksm@lamia starksm]$ netstat -an | grep LISTEN
          tcp 0 0 0.0.0.0:47461 0.0.0.0:* LISTEN *
          tcp 0 0 172.17.66.55:47462 0.0.0.0:* LISTEN
          tcp 0 0 172.17.66.55:3528 0.0.0.0:* LISTEN
          tcp 0 0 172.17.66.55:8009 0.0.0.0:* LISTEN
          tcp 0 0 172.17.66.55:1098 0.0.0.0:* LISTEN
          tcp 0 0 172.17.66.55:1099 0.0.0.0:* LISTEN
          tcp 0 0 172.17.66.55:1100 0.0.0.0:* LISTEN
          tcp 0 0 172.17.66.55:8080 0.0.0.0:* LISTEN
          tcp 0 0 172.17.66.55:8083 0.0.0.0:* LISTEN
          tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
          tcp 0 0 0.0.0.0:23 0.0.0.0:* LISTEN
          tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN
          tcp 0 0 172.17.66.55:8090 0.0.0.0:* LISTEN
          tcp 0 0 172.17.66.55:8092 0.0.0.0:* LISTEN
          tcp 0 0 172.17.66.55:4444 0.0.0.0:* LISTEN
          tcp 0 0 172.17.66.55:8093 0.0.0.0:* LISTEN
          tcp 0 0 172.17.66.55:4445 0.0.0.0:* LISTEN
          
          run.sh -c all
          [starksm@lamia starksm]$ netstat -an | grep LISTEN
          tcp 0 0 0.0.0.0:3528 0.0.0.0:* LISTEN
          tcp 0 0 0.0.0.0:8009 0.0.0.0:* LISTEN
          tcp 0 0 0.0.0.0:1098 0.0.0.0:* LISTEN
          tcp 0 0 0.0.0.0:47467 0.0.0.0:* LISTEN
          tcp 0 0 0.0.0.0:1099 0.0.0.0:* LISTEN
          tcp 0 0 0.0.0.0:1100 0.0.0.0:* LISTEN
          tcp 0 0 0.0.0.0:47468 0.0.0.0:* LISTEN
          tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN
          tcp 0 0 0.0.0.0:8083 0.0.0.0:* LISTEN
          tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
          tcp 0 0 0.0.0.0:23 0.0.0.0:* LISTEN
          tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN
          tcp 0 0 0.0.0.0:8090 0.0.0.0:* LISTEN
          tcp 0 0 0.0.0.0:8092 0.0.0.0:* LISTEN
          tcp 0 0 0.0.0.0:4444 0.0.0.0:* LISTEN
          tcp 0 0 0.0.0.0:8093 0.0.0.0:* LISTEN
          tcp 0 0 0.0.0.0:4445 0.0.0.0:* LISTEN
          



          • 2. Re: 3.2.4 cluster testsuite
            Holger Baxmann Novice

            This is mine, testsuite just finished on WinXP, java full version "1.4.2_04-b05", gives 91 errors (8 failures), most of then "connection refused" and similiar:

            one started -c all -b 192.168.1.100

            the other -c all -b 192.168.1.102

            holgerbaxmann@Tabletti ~
            $ netstat -na | grep ABH
            TCP 0.0.0.0:22 0.0.0.0:0 ABHTREN
            TCP 0.0.0.0:135 0.0.0.0:0 ABHTREN
            TCP 0.0.0.0:445 0.0.0.0:0 ABHTREN
            TCP 0.0.0.0:1025 0.0.0.0:0 ABHTREN
            TCP 0.0.0.0:3389 0.0.0.0:0 ABHTREN
            TCP 0.0.0.0:3619 0.0.0.0:0 ABHTREN
            TCP 0.0.0.0:3981 0.0.0.0:0 ABHTREN
            TCP 0.0.0.0:4371 0.0.0.0:0 ABHTREN
            TCP 0.0.0.0:5000 0.0.0.0:0 ABHTREN
            TCP 0.0.0.0:5679 0.0.0.0:0 ABHTREN
            TCP 0.0.0.0:5800 0.0.0.0:0 ABHTREN
            TCP 0.0.0.0:5900 0.0.0.0:0 ABHTREN
            TCP 0.0.0.0:44445 0.0.0.0:0 ABHTREN
            TCP 127.0.0.1:4586 0.0.0.0:0 ABHTREN
            TCP 192.168.1.100:139 0.0.0.0:0 ABHTREN
            TCP 192.168.1.100:1098 0.0.0.0:0 ABHTREN
            TCP 192.168.1.100:1099 0.0.0.0:0 ABHTREN
            TCP 192.168.1.100:1100 0.0.0.0:0 ABHTREN
            TCP 192.168.1.100:3528 0.0.0.0:0 ABHTREN
            TCP 192.168.1.100:3618 0.0.0.0:0 ABHTREN
            TCP 192.168.1.100:4444 0.0.0.0:0 ABHTREN
            TCP 192.168.1.100:4445 0.0.0.0:0 ABHTREN
            TCP 192.168.1.100:7985 0.0.0.0:0 ABHTREN
            TCP 192.168.1.100:8009 0.0.0.0:0 ABHTREN
            TCP 192.168.1.100:8080 0.0.0.0:0 ABHTREN
            TCP 192.168.1.100:8083 0.0.0.0:0 ABHTREN
            TCP 192.168.1.100:8090 0.0.0.0:0 ABHTREN
            TCP 192.168.1.100:8092 0.0.0.0:0 ABHTREN
            TCP 192.168.1.100:8093 0.0.0.0:0 ABHTREN
            TCP 192.168.1.102:139 0.0.0.0:0 ABHTREN
            TCP 192.168.1.102:1098 0.0.0.0:0 ABHTREN
            TCP 192.168.1.102:1099 0.0.0.0:0 ABHTREN
            TCP 192.168.1.102:1100 0.0.0.0:0 ABHTREN
            TCP 192.168.1.102:3528 0.0.0.0:0 ABHTREN
            TCP 192.168.1.102:3625 0.0.0.0:0 ABHTREN
            TCP 192.168.1.102:4444 0.0.0.0:0 ABHTREN
            TCP 192.168.1.102:4445 0.0.0.0:0 ABHTREN
            TCP 192.168.1.102:8009 0.0.0.0:0 ABHTREN
            TCP 192.168.1.102:8080 0.0.0.0:0 ABHTREN
            TCP 192.168.1.102:8083 0.0.0.0:0 ABHTREN
            TCP 192.168.1.102:15703 0.0.0.0:0 ABHTREN

            bax

            • 3. Re: 3.2.4 cluster testsuite
              Holger Baxmann Novice

              upps, forgot the empty one:

              holgerbaxmann@Tabletti ~
              $ netstat -na | grep ABH
              TCP 0.0.0.0:22 0.0.0.0:0 ABHTREN
              TCP 0.0.0.0:135 0.0.0.0:0 ABHTREN
              TCP 0.0.0.0:445 0.0.0.0:0 ABHTREN
              TCP 0.0.0.0:1025 0.0.0.0:0 ABHTREN
              TCP 0.0.0.0:3389 0.0.0.0:0 ABHTREN
              TCP 0.0.0.0:5000 0.0.0.0:0 ABHTREN
              TCP 0.0.0.0:5679 0.0.0.0:0 ABHTREN
              TCP 0.0.0.0:5800 0.0.0.0:0 ABHTREN
              TCP 0.0.0.0:5900 0.0.0.0:0 ABHTREN
              TCP 127.0.0.1:4586 0.0.0.0:0 ABHTREN
              TCP 192.168.1.100:139 0.0.0.0:0 ABHTREN
              TCP 192.168.1.100:7985 0.0.0.0:0 ABHTREN
              TCP 192.168.1.102:139 0.0.0.0:0 ABHTREN
              TCP 192.168.1.102:15703 0.0.0.0:0 ABHTREN

              • 4. Re: 3.2.4 cluster testsuite
                Scott Stark Master

                So those bindings look fine. What cluster testsuite are you talking about?

                • 5. Re: 3.2.4 cluster testsuite
                  Holger Baxmann Novice

                  "testsuite" target from build.bat with two nodes up on one machine

                  bax

                  • 6. Re: 3.2.4 cluster testsuite
                    Holger Baxmann Novice

                    Further investigation:

                    a) the "-b" parameter is not consistent in using hostname vs. IP, resp. getHostAddress vs. getHostName.

                    if I start "bin\run -c all -b 192.168.1.102" I will get:

                    "10:39:44,680 INFO [UDP] unicast sockets will use interface 192.168.1.100"

                    but I will not JGroup via WLAN :)

                    So he is doing a reverse lookup and ends with:

                    "GMS: address is Tabletti:3408"

                    which is really wrong.

                    And is stumbling over his feets with:

                    "10:39:46,824 INFO [DefaultPartition] New cluster view: 1 ([192.168.1.101:1099, 192.168.1.102:1099] delta: 0)"

                    remember that he finds 192.168.1.100 for Tabletti

                    so fpr example "11:48:44,968 WARN [UDP] discarded message from different group (TreeCache-Cluster). Sender was 192.168.1.100:3542" occurs

                    b) there are some occurences of "localhost" in the testsuite

                    bax

                    • 7. Re: 3.2.4 cluster testsuite
                      Holger Baxmann Novice

                      any new news about running the testsuite with two JBoss instances on one machine with multihomed NICs via "-b" parameter out of the box ?

                      thanks

                      bax

                      • 8. Re: 3.2.4 cluster testsuite
                        Holger Baxmann Novice

                        It is a bug in the 3.2.4 release JGroups config.
                        fixed for later releases,
                        see: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3837997#3837997

                        bax