1 Reply Latest reply on Oct 22, 2013 7:42 PM by Stylianos Koussouris

    TCPPING protocol not available in JBoss AS 7.2.0

    Stylianos Koussouris Newbie

      In a domain with 3 servers in full-ha profile, I have configured via CLI the following jgroups stack for TCP clustering within the profile. However, they don't seem to cluster

       

      <stack name="tcpping">
          <protocol type="TCP" socket-binding="jgroups-tcp"/>
          <protocol type="TCPPING">
              <property name="initial_hosts">
                  192.168.1.2[7600],192.168.1.3[7600]
              </property>
              <property name="port_range">
                  0
              </property>
              <property name="timeout">
                  4000
              </property>
              <property name="num_initial_members">
                  2
              </property>
          </protocol>
          <protocol type="MERGE2"/>
          <protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/>
          <protocol type="FD"/>
          <protocol type="VERIFY_SUSPECT"/>
          <protocol type="BARRIER"/>
          <protocol type="pbcast.NAKACK"/>
          <protocol type="UNICAST2"/>
          <protocol type="pbcast.STABLE"/>
          <protocol type="pbcast.GMS"/>
          <protocol type="UFC"/>
          <protocol type="MFC"/>
          <protocol type="FRAG2"/>
          <protocol type="RSVP"/>
      </stack>
      
      

       

      and as soon as I deploy and application with clustered web session an error appears as follows:

       

      01:26:56,932 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "cluster-demo.war" (runtime-name: "cluster-demo.war")
      01:26:57,192 ERROR [org.jboss.as.server] (host-controller-connection-threads - 10) JBAS015870: Deploy of deployment "cluster-demo.war" was rolled back with the following failure message:
      {"JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => {
          "Services that were unable to start:" => [
              "jboss.deployment.unit.\"cluster-demo.war\".deploymentCompleteService",
              "jboss.infinispan.web.default-host/cluster-demo",
              "jboss.infinispan.web.default-host/cluster-demo.config",
              "jboss.web.deployment.default-host./cluster-demo",
              "jboss.web.deployment.default-host./cluster-demo.session"
          ],
          "Services that may be the cause:" => ["jboss.jgroups.stack.tcpping"]
      
      

       

      I also noticed that TCPPING is also not an option in creating the stack via the Admin Console. Can anyone advice

      a) Is TCPPING available?

      b) Is there something wrong with the above configuration

      c) If not TCPPING what other protocol will guarantee point-to-point message distribution via TCP?

        • 1. Re: TCPPING protocol not available in JBoss AS 7.2.0
          Stylianos Koussouris Newbie

          I identified the issue on the above configuration to the following

          <protocol type="TCP" socket-binding="jgroups-tcp"/>
          

           

          which should be

          <transport type="TCP" socket-binding="jgroups-tcp"/>
          

           

          However, the issue stems from the fact that I could not run the batch to create it whilst also remains the question why the the TCPPING protocol is not available via the Admin Console

           

          [domain@192.168.1.2:9999 /] batch
          [domain@192.168.1.2:9999 / #] cd /profile=full-ha/subsystem=jgroups
          [domain@192.168.1.2:9999 subsystem=jgroups #] ./stack=tcpping:add
          #1 /profile=full-ha/subsystem=jgroups/stack=tcpping:add
          [domain@192.168.1.2:9999 subsystem=jgroups #] cd stack=tcpping
          JBAS014808: Child resource '"stack" => "tcpping"' not found
          [domain@192.168.1.2:9999 subsystem=jgroups #] ./transport=TCP:add(type=TCP,socket-binding=jgroups-tcp)
          #2 /profile=full-ha/subsystem=jgroups/transport=TCP:add(type=TCP,socket-binding=jgroups-tcp)
          [domain@192.168.1.2:9999 subsystem=jgroups #] :add-protocol(type=TCPPING)
          #3 /profile=full-ha/subsystem=jgroups:add-protocol(type=TCPPING)
          [domain@192.168.1.2:9999 subsystem=jgroups #] :add-protocol(type=MERGE2)
          #4 /profile=full-ha/subsystem=jgroups:add-protocol(type=MERGE2)
          [domain@192.168.1.2:9999 subsystem=jgroups #] :add-protocol(type=FD_SOCK,socket-binding=jgroups-tcp-fd)
          #5 /profile=full-ha/subsystem=jgroups:add-protocol(type=FD_SOCK,socket-binding=jgroups-tcp-fd)
          [domain@192.168.1.2:9999 subsystem=jgroups #] :add-protocol(type=FD)
          #6 /profile=full-ha/subsystem=jgroups:add-protocol(type=FD)
          [domain@192.168.1.2:9999 subsystem=jgroups #] :add-protocol(type=VERIFY_SUSPECT)
          #7 /profile=full-ha/subsystem=jgroups:add-protocol(type=VERIFY_SUSPECT)
          [domain@192.168.1.2:9999 subsystem=jgroups #] :add-protocol(type=BARRIER)
          #8 /profile=full-ha/subsystem=jgroups:add-protocol(type=BARRIER)
          [domain@192.168.1.2:9999 subsystem=jgroups #] :add-protocol(type=pbcast.NAKACK)
          #9 /profile=full-ha/subsystem=jgroups:add-protocol(type=pbcast.NAKACK)
          [domain@192.168.1.2:9999 subsystem=jgroups #] :add-protocol(type=UNICAST2)
          #10 /profile=full-ha/subsystem=jgroups:add-protocol(type=UNICAST2)
          [domain@192.168.1.2:9999 subsystem=jgroups #] :add-protocol(type=pbcast.STABLE)
          #11 /profile=full-ha/subsystem=jgroups:add-protocol(type=pbcast.STABLE)
          [domain@192.168.1.2:9999 subsystem=jgroups #] :add-protocol(type=pbcast.GMS)
          #12 /profile=full-ha/subsystem=jgroups:add-protocol(type=pbcast.GMS)
          [domain@192.168.1.2:9999 subsystem=jgroups #] :add-protocol(type=UFC)
          #13 /profile=full-ha/subsystem=jgroups:add-protocol(type=UFC)
          [domain@192.168.1.2:9999 subsystem=jgroups #] :add-protocol(type=MFC)
          #14 /profile=full-ha/subsystem=jgroups:add-protocol(type=MFC)
          [domain@192.168.1.2:9999 subsystem=jgroups #] :add-protocol(type=FRAG2)
          #15 /profile=full-ha/subsystem=jgroups:add-protocol(type=FRAG2)
          [domain@192.168.1.2:9999 subsystem=jgroups #] :add-protocol(type=RSVP)
          #16 /profile=full-ha/subsystem=jgroups:add-protocol(type=RSVP)
          [domain@192.168.1.2:9999 subsystem=jgroups #] cd protocol=TCPPING
          JBAS014808: Child resource '"protocol" => "TCPPING"' not found
          [domain@192.168.1.2:9999 subsystem=jgroups #] ./property=initial_hosts/:add(value="192.168.1.2[7600],192.168.1.3[7600]")
          #17 /profile=full-ha/subsystem=jgroups/property=initial_hosts:add(value="192.168.1.2[7600],192.168.1.3[7600]")
          [domain@192.168.1.2:9999 subsystem=jgroups #] ./property=port_range/:add(value=0)
          #18 /profile=full-ha/subsystem=jgroups/property=port_range:add(value=0)
          [domain@192.168.1.2:9999 subsystem=jgroups #] ./property=timeout/:add(value=4000)
          #19 /profile=full-ha/subsystem=jgroups/property=timeout:add(value=4000)
          [domain@192.168.1.2:9999 subsystem=jgroups #] ./property=num_initial_members/:add(value=2)
          #20 /profile=full-ha/subsystem=jgroups/property=num_initial_members:add(value=2)
          [domain@192.168.1.2:9999 subsystem=jgroups #] cd ../..
          [domain@192.168.1.2:9999 / #] :write-attribute(name=default-stack,value=tcpping)
          #21 /:write-attribute(name=default-stack,value=tcpping)
          [domain@192.168.1.2:9999 / #] run-batch
          JBAS014883: No resource definition is registered for address [
              ("profile" => "full-ha"),
              ("subsystem" => "jgroups"),
              ("transport" => "TCP")
          ]