Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-8153 Upgrade HornetQ for EAP 5.2.0
  3. JBPAPP-8578

Discovery group binds to 0.0.0.0 on all OSs even though local-bind-address is set

    XMLWordPrintable

Details

    • Sub-task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Done
    • EAP_EWP 5.1.2
    • EAP_EWP 5.2.0
    • HornetQ
    • None
    • Release Notes
    • Hide
      It was found that a <literal>discovery-group</literal> would effectively ignore the <literal>group-address</literal> and simply bind to <uri>0.0.0.0</uri>. This could potentially lead to cluster "cross-talk" where applications listening on a MulticastSocket receive packets associated with a different multicast address. The problem was caused by EAP using the wrong constructor for <code>java.net.MulticastSocket</code>. A patch has ensured EAP uses the correct constructor and adds a log message to warn the user if the expected configuration failed.
      Show
      It was found that a <literal>discovery-group</literal> would effectively ignore the <literal>group-address</literal> and simply bind to <uri>0.0.0.0</uri>. This could potentially lead to cluster "cross-talk" where applications listening on a MulticastSocket receive packets associated with a different multicast address. The problem was caused by EAP using the wrong constructor for <code>java.net.MulticastSocket</code>. A patch has ensured EAP uses the correct constructor and adds a log message to warn the user if the expected configuration failed.
    • Documented as Resolved Issue
    • NEW

    Attachments

      Activity

        People

          rhn-support-jbertram Justin Bertram
          rhn-support-jbertram Justin Bertram
          Scott Thomas Scott Thomas (Inactive)
          Votes:
          0 Vote for this issue
          Watchers:
          3 Start watching this issue

          Dates

            Created:
            Updated:
            Resolved: