Problem with HAJNDI with JBoss clustering

agohar Apr 9, 2008 10:32 AM

Hi,

I am having issues in looking up the resources (Queues etc) in HAJNDI at port 1100 on localhost with my jboss servers split across a cluster spanning different networks (different subnets). We have jboss servers on each side of network and they are able to join a single cluster without any issue. JBoss and Java version is same on all servers, which is jboss-4.0.2 and java 5.

When look up is performed on a non master node, it just hangs up. Whereas it works fine on a master node.

Here is the network setup:

we have 2 VLANs, separated by Cisco routers and the routers are using PIMv2 in sparse mode, with a Rendezvous Point configured on each side of the intersite link. Multicast routing between the vlans is handled by the routers. The routers can see the servers joining the multicast groups, and that is reflected in the servers on each vlan joining the same cluster, as shown in the log files.

Any help will be appreciated.

Thank you.

1. Re: Problem with HAJNDI with JBoss clustering

brian.stansberry Apr 9, 2008 12:13 PM (in response to agohar)

When you say it "hangs up", is this basically a case where the lookup hangs for 60 seconds and then you get a NameNotFoundException?

If that's the case, it sounds like an intermittent connectivity issue; i.e. enough messages are able to get through that the servers are able to form a cluster, but the RPCs or RPC responses used for the cluster-wide HA-JNDI lookups are not getting through. Effect is the node doing the lookup waits 60 secs for responses that never arrive, then throws NameNotFoundException. If the servers weren't forming a cluster at all, you'd get NNFE, but it would happen quickly.

See http://wiki.jboss.org/wiki/TestingJBoss and the multicast sender/receiver tests described at http://www.jgroups.org/javagroupsnew/docs/manual/html/ch02.html#ItDoesntWork for help in tracking down multicast issues.

You can also consider using a TCP-based stack. If you want dynamic discovery of members and find multicast is working well enough for that, you can consider using MPING as your discovery protocol in a TCP-based stack. See http://wiki.jboss.org/wiki/JGroupsMPING .
Actions