Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-7113

Diagnostic address mismatch between channels and Probe client

    Details

    • Similar Issues:
      Show 10 results 

      Description

      Bela Ban wrote:
      > (probe.sh) uses the wrong port 224.0.0.75 instead of 224.0.75.75. This needs to be
      > changed, either by upgrading jgroups.jar or by adding "
      >
      > -addr 224.0.75.75 $*"
      >
      > to jboss-5.1.0.GA/bin/probe.sh
      >

        Gliffy Diagrams

          Issue Links

            Activity

            Hide
            brian.stansberry Brian Stansberry added a comment -

            This one confused me, since for a long time org.jgroups.tests.Probe used 224.0.75.75 as the default, and that was the default address in TP as well.

            Now I see the issue: it's that the AS's stacks.xml is using the wrong default address in all its TP configs: diagnostics_addr="$

            {jboss.jgroups.diagnostics_addr:224.0.0.75}

            "

            Easiest fix is to correct the -stacks.xml.

            Show
            brian.stansberry Brian Stansberry added a comment - This one confused me, since for a long time org.jgroups.tests.Probe used 224.0.75.75 as the default, and that was the default address in TP as well. Now I see the issue: it's that the AS's stacks.xml is using the wrong default address in all its TP configs: diagnostics_addr="$ {jboss.jgroups.diagnostics_addr:224.0.0.75} " Easiest fix is to correct the -stacks.xml.
            Hide
            brian.stansberry Brian Stansberry added a comment -

            Haha, Jimmy Wilson explained it all to me. There was a code mismatch in JGroups 2.4 (see JGRP-880), but it was fixed in JGroups 2.6 long ago. So the original problem description is out-of-date. However, investigating this made me realize the AS stacks.xml is incorrect.

            Show
            brian.stansberry Brian Stansberry added a comment - Haha, Jimmy Wilson explained it all to me. There was a code mismatch in JGroups 2.4 (see JGRP-880 ), but it was fixed in JGroups 2.6 long ago. So the original problem description is out-of-date. However, investigating this made me realize the AS stacks.xml is incorrect.
            Hide
            brian.stansberry Brian Stansberry added a comment -

            JBAS-6873 introduced the incorrect configuration in -stacks.xml problem.

            Show
            brian.stansberry Brian Stansberry added a comment - JBAS-6873 introduced the incorrect configuration in -stacks.xml problem.
            Hide
            brian.stansberry Brian Stansberry added a comment -

            Reopen to correct Fix Version

            Show
            brian.stansberry Brian Stansberry added a comment - Reopen to correct Fix Version

              People

              • Assignee:
                brian.stansberry Brian Stansberry
                Reporter:
                brian.stansberry Brian Stansberry
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Development