Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-7418

JGroups MPING configurations in JBoss EAP don't use jboss.partition.udpGroup

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: EAP_EWP 5.1.1, EAP_EWP 5.1.2
    • Fix Version/s: EAP_EWP 5.2.0
    • Component/s: Clustering
    • Labels:
      None
    • Steps to Reproduce:
      Hide

      Start a default EAP 5.1.1 installation with "run.sh -c production -u 230.5.6.7".

      Expected results: All JGroups multicast communication uses 230.5.6.7
      Actual results: JBoss Messaging data channel's MPING uses its default 228.6.6.6.

      Show
      Start a default EAP 5.1.1 installation with "run.sh -c production -u 230.5.6.7". Expected results: All JGroups multicast communication uses 230.5.6.7 Actual results: JBoss Messaging data channel's MPING uses its default 228.6.6.6.
    • Affects:
      Release Notes
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      Set the appropriate system property for each channel using MPING.
      For JBoss Messaging data channel, this is jboss.jgroups.jbm_data.mping_mcast_addr.

      Show
      Set the appropriate system property for each channel using MPING. For JBoss Messaging data channel, this is jboss.jgroups.jbm_data.mping_mcast_addr.
    • Release Notes Text:
      Hide
      The JGroups MPING configurations ignored the jboss.partition.udpGroup system property (set with the -u option). Therefore, when setting the multicast address for clustering using -u, any channels using MPING, such as the JBoss Messaging data channel, used the default address instead of the configured address. The jboss.partition.udpGroup property has been added to the MPING configuration in the binding manager and setting the multicast address for clustering using -u now affects all clustering channels as expected.
      Show
      The JGroups MPING configurations ignored the jboss.partition.udpGroup system property (set with the -u option). Therefore, when setting the multicast address for clustering using -u, any channels using MPING, such as the JBoss Messaging data channel, used the default address instead of the configured address. The jboss.partition.udpGroup property has been added to the MPING configuration in the binding manager and setting the multicast address for clustering using -u now affects all clustering channels as expected.
    • Release Notes Docs Status:
      Documented as Resolved Issue
    • Docs QE Status:
      NEW

      Description

      The fixes in EAP 5.1.1 for JBPAPP-6011 inadvertently removed jboss.partition.udpGroup from the JGroups MPING configurations in the binding manager.
      Because of this, setting jboss.partition.udpGroup, or run.sh "-u" no longer sets the MPING multicast address.

      This affects backwards compatibility with EAP 5.0, 5.0.1, and 5.1.
      It mainly affects the JBoss Messaging data channel, as that's typically the only channel using MPING.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                dereed Dennis Reed
                Reporter:
                dereed Dennis Reed
                Writer:
                Eva Kopalova
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: