2 Replies Latest reply on Aug 14, 2018 4:39 AM by mylos78

    Unable to use JGroups' Probe with WildFly

    mylos78

      Hi all!

      I'd need to use JGroups' probe.sh to verify the network transmission in my cluster. I can see from the docs that "probe.sh" can be also launched via org.jgroups.tests.Probe, so on WildFly 13 running a cluster I have executed:

      java -cp ./org/jgroups/main/jgroups-4.0.11.Final.jar -Djava.net.preferIPv4Stack=true org.jgroups.tests.Probe

      The result, however is always:

      0 responses (0 matches, 0 non matches)

      Also when forcing WildFly's UDP address/port the result is the same:

      java -cp ./org/jgroups/main/jgroups-4.0.11.Final.jar -Djava.net.preferIPv4Stack=true org.jgroups.tests.Probe -addr 230.0.0.4 -port 55200
      0 responses (0 matches, 0 non matches)

      Do you know what could be possible wrong with that ?

      Thanks!

        • 1. Re: Unable to use JGroups' Probe with WildFly
          rhusar

          Hi Mylos,

           

          JGroups diagnostics which can be accessed with probe utility is disabled by default. IIRC probe does not have any security (or very limited), so having it open is insecure.

           

          To enable diagnostics, first add the socket binding then configure the desired stack to listen for probes, e.g.:

           

           

          /socket-binding-group=standard-sockets/socket-binding=jgroups-diagnostics:add(multicast-address="${jboss.jgroups.diagnostics_addr:224.0.0.75}",multicast-port="${jboss.jgroups.diagnostics_port:7500}")
          /subsystem=jgroups/stack=tcp/transport=TCP:write-attribute(name=diagnostics-socket-binding,value=jgroups-diagnostics)
          • 2. Re: Unable to use JGroups' Probe with WildFly
            mylos78

            Thanks for your kind reply Radoslav!