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.