Hi, I'm not sure if this is a bug or if it is working to spec....
My JBoss application has a JChannel that connects to groupname "ScheduleBroadcaster", and the JChannel is created with the multicast address is 188.8.131.52
If I start a second instance of my JBoss application, which also has the JChannel connecting to groupname "ScheduleBroadcaster" but created the JChannel with a DIFFERENT multicast address ie. 184.108.40.206, should they be able to receive each other's messages?
What I'm seeing is that they do receive each other's messages. I'm not sure if this is expected, or if perhaps I have things configured wrong network-wise.
Thanks for whoever knows this answer.
First of all, 221.X.X.X is not a valid class D address.
Second, all members have to have the same mcast address.
Thank you Bela. That isn't the address, I just threw numbers out there, guess I should pay better attention to detail! To be perfectly correct, the properties are:
From your answer I am still unclear. You say the multicast addresses of members of the group have to be the same. Is "have to be" a strict requirement, or a suggestion?
I'm trying to find out what expected behaviour is versus what I'm seeing. I'm seeing two JChannels with the same group name but different multicast addresses (substitute the above 220.127.116.11 with 18.104.22.168 for the second app) talk to each other.
What is expected behaviour when the multicast addresses are different but the JChannel groupname is the same? Is it a bug that introduces indeterminate behaviour, or do you expect them to be able to send messages in isolation from each other, or do you expect what I'm seeing, in that they receive each other's messages? My ip resolution may be the problem, but I need to know what expected behaviour is. Thanks, Bela.
2 members talking on different multicast addresses (despite having the same group names, and the same mcast ports) will *not* talk to each other.
Your config above doesn't have any GMS in it anyway, so member won't find each other.
sorry, that code example wasn't perfectly correct, I missed the port number 2000, oh well
Thanks, that clears up the issue, I was pretty sure the cross-pollution of messages was due to an address resolution problem and not JChannel, now I have a better idea of how it works. Thanks again.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.