[jboss-jira] [JBoss JIRA] Commented: (JGRP-515) UDP.java requires the multicast address in the multicastsocket constructor to fix crosstalk on certain operating systems
ggimler (JIRA)
jira-events at lists.jboss.org
Fri May 18 09:31:54 EDT 2007
[ http://jira.jboss.com/jira/browse/JGRP-515?page=comments#action_12362508 ]
ggimler commented on JGRP-515:
------------------------------
If I run it then it works for me on Fedora Core 6 with JDK 1.5.0_10 and it works on Redhat Enterprise AS release 4 Update 3. I am creating the socket with 225.0.6.12. I haven't tried Windows yet.
ggimler at dacia:~/workspace/perseus/bin$ ./mcastrcv reliable 225.0.6.12 14001 1000 192.168.101.*
Receiving data in reliable mode with JGroups.
received 0 messages. Average latency = 0 ms
May 18, 2007 9:25:35 AM org.jgroups.JChannel init
INFO: JGroups version: 2.4.1 SP-3
May 18, 2007 9:25:35 AM org.jgroups.protocols.FRAG2 setProperties
INFO: frag_size=60000, overhead=200, new frag_size=59800
May 18, 2007 9:25:35 AM org.jgroups.protocols.FRAG2 up
INFO: received CONFIG event: {bind_addr=/192.168.101.133}
May 18, 2007 9:25:35 AM org.jgroups.protocols.UDP createSockets
INFO: sockets will use interface 192.168.101.133
May 18, 2007 9:25:35 AM org.jgroups.protocols.UDP createSockets
INFO: socket information:
local_addr=192.168.101.133:32789, mcast_addr=225.0.6.12:14001, bind_addr=/192.168.101.133, ttl=32
sock: bound to 192.168.101.133:32789, receive buffer size=131071, send buffer size=131071
mcast_recv_sock: bound to 192.168.101.133:14001, send buffer size=131071, receive buffer size=131071
mcast_send_sock: bound to 192.168.101.133:32791, send buffer size=131071, receive buffer size=131071
-------------------------------------------------------
GMS: address is 192.168.101.133:32789
-------------------------------------------------------
received 0 messages. Average latency = 0 ms
received 0 messages. Average latency = 0 ms
received 0 messages. Average latency = 0 ms
received 0 messages. Average latency = 0 ms
received 0 messages. Average latency = 0 ms
received 0 messages. Average latency = 0 ms
May 18, 2007 9:25:41 AM org.jgroups.protocols.pbcast.CoordGmsImpl handleMembershipChange
INFO: Successful GMS flush by coordinator at 192.168.101.133:32789
received 3 messages. Average latency = 106 ms
received 13 messages. Average latency = 0 ms
received 22 messages. Average latency = 0 ms
received 32 messages. Average latency = 0 ms
received 34 messages. Average latency = 0 ms
ggimler at dacia:~/workspace/perseus/bin$ /sbin/route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.101.0 * 255.255.255.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth0
default 192.168.101.1 0.0.0.0 UG 0 0 0 eth0
> UDP.java requires the multicast address in the multicastsocket constructor to fix crosstalk on certain operating systems
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: JGRP-515
> URL: http://jira.jboss.com/jira/browse/JGRP-515
> Project: JGroups
> Issue Type: Patch
> Environment: Tested on Fedora Core 6, JDK 1.5.0_10
> Reporter: ggimler
> Assigned To: Bela Ban
> Fix For: 2.5
>
> Attachments: UDP.java
>
>
> 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:
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list