1 Reply Latest reply on Jan 19, 2007 4:13 AM by belaban

    Problem with TCP config

      Hello,

      I'm currently trying to create a working JGoups configuration using TCP. I'm using the Draw application to test :

      This is my config at HOST A :

      <config>
       <TCP start_port="9999"/>
       <TCPPING initial_hosts="192.168.0.136[9999],192.168.0.175[9999]" port_range="1"
      
      timeout="3000" num_initial_members="1" up_thread="true" down_thread="true" />
       <FD shun="true" up_thread="true" down_thread="true" timeout="2500" max_tries="5" />
       <VERIFY_SUSPECT timeout="1500" up_thread="false" down_thread="false" />
       <pbcast.NAKACK gc_lag="100" retransmit_timeout="3000" up_thread="true" down_thread="true"
      
      />
       <pbcast.STABLE desired_avg_gossip="20000" up_thread="false" down_thread="false" />
       <pbcast.GMS join_timeout="5000" join_retry_timeout="2000" shun="false"
      
      print_local_addr="true" down_thread="true" up_thread="true" />
       <pbcast.STATE_TRANSFER up_thread="true" down_thread="true" />
       </config>


      This is the config on Host B :

      <config>
       <TCP start_port="9999"/>
       <TCPPING initial_hosts="192.168.0.175[9999],192.168.0.136[9999]" port_range="1" timeout="3000" num_initial_members="1" up_thread="true" down_thread="true" />
       <FD shun="true" up_thread="true" down_thread="true" timeout="2500" max_tries="5" />
       <VERIFY_SUSPECT timeout="1500" up_thread="false" down_thread="false" />
       <pbcast.NAKACK gc_lag="100" retransmit_timeout="3000" up_thread="true" down_thread="true" />
       <pbcast.STABLE desired_avg_gossip="20000" up_thread="false" down_thread="false" />
       <pbcast.GMS join_timeout="5000" join_retry_timeout="2000" shun="false" print_local_addr="true" down_thread="true" up_thread="true" />
       <pbcast.STATE_TRANSFER up_thread="true" down_thread="true" />
       </config>


      It seems the members don't see eachother.

      This is the logging I get on host A :

      18-jan-2007 23:42:05 org.jgroups.blocks.ConnectionTable start
      INFO: server socket created on AWS00581:9999
      
      -------------------------------------------------------
      GMS: address is AWS00581:9999
      -------------------------------------------------------
      18-jan-2007 23:42:05 org.jgroups.blocks.ConnectionTable run
      INFO: accepted connection, client_sock=Socket[addr=/192.168.0.136,port=1628,localport=9999]
      18-jan-2007 23:42:05 org.jgroups.blocks.ConnectionTable$Connection matchCookie
      INFO: input_cookie is bela
      18-jan-2007 23:42:05 org.jgroups.blocks.ConnectionTable$Connection init
      INFO: connection was created to AWS00581:9999
      18-jan-2007 23:42:05 org.jgroups.blocks.ConnectionTable getConnection
      INFO: created socket to AWS00581:9999
      18-jan-2007 23:42:05 org.jgroups.blocks.ConnectionTable$Connection init
      INFO: connection was created to AWS00581:9999
      ** View=[AWS00581:9999|0] [AWS00581:9999]
      18-jan-2007 23:42:16 org.jgroups.blocks.ConnectionTable run
      INFO: accepted connection, client_sock=Socket[addr=/192.168.0.175,port=3092,localport=9999]
      18-jan-2007 23:42:16 org.jgroups.blocks.ConnectionTable$Connection matchCookie
      INFO: input_cookie is bela
      18-jan-2007 23:42:21 org.jgroups.blocks.ConnectionTable$Connection init
      INFO: connection was created to BLACKLIGHT:9999


      This is the logging I get on Host B :

      18-jan-2007 23:42:05 org.jgroups.blocks.ConnectionTable start
      INFO: server socket created on blacklight:9999
      
      -------------------------------------------------------
      GMS: address is blacklight:9999
      -------------------------------------------------------
      18-jan-2007 23:42:05 org.jgroups.blocks.ConnectionTable run
      INFO: accepted connection, client_sock=Socket[addr=/192.168.0.175,port=3091,localport=9999]
      18-jan-2007 23:42:05 org.jgroups.blocks.ConnectionTable$Connection matchCookie
      INFO: input_cookie is bela
      18-jan-2007 23:42:05 org.jgroups.blocks.ConnectionTable$Connection init
      INFO: connection was created to 192.168.0.175:9999
      18-jan-2007 23:42:05 org.jgroups.blocks.ConnectionTable getConnection
      INFO: created socket to 192.168.0.175:9999
      18-jan-2007 23:42:05 org.jgroups.blocks.ConnectionTable$Connection init
      INFO: connection was created to 192.168.0.175:9999
      ** View=[blacklight:9999|0] [blacklight:9999]
      18-jan-2007 23:42:09 org.jgroups.blocks.ConnectionTable$Connection init
      INFO: connection was created to 192.168.0.136:9999
      18-jan-2007 23:42:09 org.jgroups.blocks.ConnectionTable getConnection
      INFO: created socket to 192.168.0.136:9999
      


      The member list contains on both hosts only one machine. Because of this the state in the Draw application is not transfered.

      Extra info :

      Host A : 192.168.0.136 = AWS00581
      Host B : 192.168.0.175 = BLACKLIGHT

      Can somebody please shed a light in here?

      Kind regards and thanks in advance for helping me out.

      Johan

        • 1. Re: Problem with TCP config
          belaban

          Can you try with the tcp.xml config from the JGroups/conf dir (part of the source distro of JGroups) ?
          I also suggest setting the bind_addr option in the config file, or using the -Dbind.address=1.2.3.4 property