It doesn't make a lot of differences whether you're running Windows or Linux.
For JBoss EAP, you can use either standalone mode, or domain mode (just make sure use HA or Full-HA profile), depending on your setup and preferences.
For load balance, mod_cluster is recommended.
>> How can i balance load and avoid fail-over.
So you don't want fail-over ?
Thanks for your links!!
Sorry,I have framed wrong statement "how can i balance load and avoid fail-over."
My requirement is, Whenever My Application server1 goes down, requests should redirect to App Server2 without any downtime.
Or can you advise me what if i use both Active App servers, i mean both app servers should be up and running distributing the requests from Apache.
What would be the better way to pursue?
The 2 links I gave in my last comment should be what you're after, if I'm understanding your requirements correctly.
Build up a test env. and follow those link to do a lab you'll understand how it works.
"AS7 Cluster Howto" uses domain mode which is convenient to manage multiple jboss instances (especially when you have more than 4 or 5 nodes)
But if there are only 2 nodes then I'd prefer standalone mode, easy to start with... you can google this and there are plenty of blogs / examples for setting up EAP6/JBossAS7 cluster in standalone mode.
Once setup the cluster and mod_cluster, you can test load-balancing / failover / session replication.
Session replication is enabled by adding the <distributable/> tag in your app deployment (with JBoss using "-ha" profile of course), you don't have to use session replication, if it's not required in your env./app.
(from your description you need load balance and fail over only ?)
Yes, i need only load balance and fail over.
I don't have much knowledge of session replication,great if you would share some light on it.
I will follow links provided by you and start testing.Thanks.