[
https://jira.jboss.org/jira/browse/JGRP-862?page=com.atlassian.jira.plugi...
]
Bela Ban resolved JGRP-862.
---------------------------
Resolution: Rejected
This is because the MulticastReceiverTest does not use the 'right'
MulticastSocket() constructor. It uses
new MulticastSocket(PORT)
If you take a look at UDP.createSockets(), the multicast socket is created through
Util.createMulticastSocket() and there we use the mcast address as bind address.
The cross talking issue was fixed in 2.7 and 2.6.6 ().
So if you use 2.6.6 and run the Draw demo with your mcast_addrs, this issue won't pop
up
JGroups appears to ignore the multicast address when more than one
jgoup application is running on the same machine.
--------------------------------------------------------------------------------------------------------------------
Key: JGRP-862
URL:
https://jira.jboss.org/jira/browse/JGRP-862
Project: JGroups
Issue Type: Bug
Affects Versions: 2.6.6
Environment: Linxu AS4, Jgroups-2.6.6 , Java version "1.5.0_10"
Reporter: Brendan Doherty
Assignee: Bela Ban
Fix For: 2.6.7
Using the multicast send/receiver test application, all on the same physical machine with
the following parameters -Djava.net.preferIPv4Stack=true -mcast_addr <AS BELOW>
-bind_addr <LAN IP address>
Create one sender on 239.197.0.1
Create one receiver on 239.198.0.1
Create a second receiver on 239.199.0.1
Send a message, as expected neither of the receivers observe the message.
Create a third receiver on 239.197.0.1
Send a message, all three senders now receive the message
Is this the expected behaviour?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira