"akostadinov" wrote : | | Yes, I see that now. Do you have a test to check it is working so a RHEL bugzilla can be filed? | I don't think this is a bug, as each member does receive their own messages. However, the *peer* members don't receive messages ! anonymous wrote : | Yes, I mean network interface not be specified as things seem to always work that way. And that leads to multicast setup not being so much error prone. | Do you see any drawbacks of having that by default for JBoss AS 5? | Not picking a NIC leads to issues in the ATL labs (at least clusterxx.qa.atl.jboss.com): you *have* to use the virtual NICs assigned to you (e.g. MYTESTIP_1), otherwise the members won't see each other. In addition, you also have to pick the 'right' IP multicast address, in order to send your traffic to the correct switch/router (MB, GB). I don't know if this changed recently. If not, maybe we should ask the IT folks to assign a *reserved* NIC for Hudson's test runs and possibly a routing entry for a specific multicast address... Comments ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102247#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...