1 Reply Latest reply on Sep 14, 2010 2:08 AM by wdfink

AutoDiscovery of IP failure

mallalli Sep 14, 2010 2:07 AM

Hi Experts,

I am using jboss 5.1 with JBM 1.4.3.I am facing problems with auto discovery of other clusters.

Scenario 1

Suppose i run 1 jboss instance as

1) run.sh -c all -b 10.10.10.198 -Djboss.messaging.ServerPeerID=99

other instance as

2)run.sh -c all -b 10.10.10.110 -Djboss.messaging.ServerPeerID=100,

then the auto discovery of the each clusters happen and i can see the log in both servers. Both the ips 10.10.10.198,10.10.10.110 are in local network and it works fine.

log

18:53:54,512 INFO [GroupMember] New Members : 1 ([10.10.10.198:51546])

18:53:54,512 INFO [GroupMember] All Members : 2 ([10.10.10.198:51546], [10.10.10.110:51526])

Scenario 2

Suppose if i try similar thing in with our REMOTE machines

1) run.sh -c all -b 17.10.15.122 -Djboss.messaging.ServerPeerID=99

2) run.sh -c all -b 17.10.220.12 -Djboss.messaging.ServerPeerID=100

Then the instance running at 17.10.15.122 is not communicating with instance running at 17.10.220.12. Auto discovery fails.

Questions

1) Why is the auto discovery failing in scenario 2.?

2) Is there any config that i have missed that makes auto discovery fails.?

3) How do i make the two instance running at different IP communicate?

Please help me on this.

Thanks

Shivaraj

18:53:54,512 INFO [GroupMember] New Members : 1 ([10.10.10.198:51546])

18:53:54,512 INFO [GroupMember] All Members : 1 ([10.10.10.198:51546])

1) run.sh -c all -b 17.10.15.122 -Djboss.messaging.ServerPeerID=99

1. Re: AutoDiscovery of IP failure

wdfink Sep 14, 2010 2:08 AM (in response to mallalli)

Probably that depends to the network topologie.
Network switches often suppress broadcasting to avoid traffic.
The Multicast addresses (224.0.0.0 to 239.255.255.255 wikipedia will give mor info)
might blocked if you cross a switch with a different sub-network address.
Actions