Uploaded image for project: 'JGroups'
  1. JGroups
  2. JGRP-515

UDP.java requires the multicast address in the multicastsocket constructor to fix crosstalk on certain operating systems

    XMLWordPrintable

Details

    • Patch
    • Resolution: Won't Do
    • Major
    • 2.5
    • None
    • None

    Description

      I'm submitting a patch for a crosstalk issue described below.

      I'm trying to debug a problem I'm seeing when running JGroups on the
      same network/machine as another application that is sending/receiving
      data via regular multicast (not through JGroups). I'm using version
      2.4.1-SP3. My scenario is as follows...

      JGroups send on 228.0.0.1:50000
      JGroups receive on 228.0.0.1:50000

      This works fine. When I start up another application that does

      Sends regular multicast on 228.0.0.2:50000
      Receives regular multicast on 228.0.0.2:50000

      Then the JVM with the JGroups sender/receiver complains with:

      May 15, 2007 4:47:59 PM org.jgroups.protocols.TP handleIncomingPacket
      WARNING: packet from 192.168.101.133:36594 has different version
      (26725) from ours (2.4.1). Packet is discarded

      The patch is in UDP.java:

      Attachments

        1. mcreceive.c
          4 kB
        2. mcsend.c
          3 kB
        3. UDP.java
          37 kB

        Issue Links

          is duplicated by

          Task - Represents a small unit of work that is not end-user facing. JGRP-516 UDP: mcast_sock is not binding to bind_addr for reception of packets

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rhn-engineering-bban Bela Ban
              ggimler_jira ggimler (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: