monasehgal, are you sure that you have any kind of load balancing mechanism in front of those two JBoss/Tomcat machine? (ie. Hardware L4/L7 switch or Web Server plugin kind thing)
There is no way to get fail-over with no load balancer.
I'm new to JBoss and haven't experimented much with it yet, but I read in the Clustering manual that it has smart proxies that use RMI to do failover. Am I misunderstanding the documentation?
However, it does say that non-RMI clients seem to loose the clustering feature. Could this be the problem?
Refer to P.20 of the manual.
Yes. that EJB stub dose the job doen *for EJB requset*.
There should be other *for HTTP request*. Something like H/W L4 switch.
Does anything need to be done to use the smart proxies? We are experiencing the same problems as monasehgal.
Our problem is that there appears to be no load balancing and no failover. Whichever JBoss node starts up last seems to take all of the work (we've tried using round/random robin and first available). When the server doing all the work is shut down (cleanly) no failover happens and the client gets very unhappy. The only time I've managed to get any kind of failover is when I touch my files in the farm dir (as the second node can take a while to redeploy the new files). In this case I see the busy node undeploy it's files and start using the other node (which has already deployed the new archives).
If I do another test by pulling the network cable out of the busy node everything hangs until it becomes available again. The other server detects the loss of the node but the clients don't (this seems most worrying when I am using first available).
Just for reference we are trying this using the auto-detection so java.naming.provider.url=""
to help us:
- provide your full jboss version (we expect you to use a *recent* version)
- modify one of your methods you call to simply have this in its body:
throw new Exception ();
and send the exceptions you see BOTH on the server AND on the client.