multi-homed, multi-app jboss cluster only partially working

[awclemen]

Hello Forum Folks,

I'm running Jboss 4.0.4GA.

I have two servers Server1 and Server2. Each server has two IPs on one NIC, IPServer1-1, IPServer1-2 for Server1 and IPServer2-1, IPServer2-2 for Server2. I have two apps running on the servers App1 and App2. App1 handles requests from first set of IPs (IPServer1-1 & IPServer2-1) and App2 handles requests from the second set of IPs (IPServer1-2 & IPServer2-2). The reason for this is I have seperate SSL certificates for each application. I have a Cisco box doing the load-balancing using sticky sessions and it does fail-over when a JBoss server is brought down.

Now, when I bring down one server, App1 correctly fails over (i.e. the session continues on the other server). However, App2 does not.

The first question I have is, Is possible to have this type of fail-over for both applications or do I need to create different JBoss instances for each application?

Secondly, if this is possible, What am I doing wrong? I suspect it has something to do with the binding of the IP with the clustering service.
Currently, I have not bound the clustering service to any IP address and the logs show that the clustering is working on the first set of IPs (where App1 is correctly working for fail-over). Can I bind the clustering service to mulitple IP addresses? If so, how?

Thanks in advance for your time and effort.

--Andy

[brian.stansberry]

You can bind to both interfaces (see http://wiki.jboss.org/wiki/Wiki.jsp?page=JGroupsUDP) but I highly doubt that's your problem. What network the inter-server clustering traffic runs on is unrelated to what network the client requests are running on. You say App1 fails over; I assume you mean that the session is replicated and available on the the other server. If so, that means session replication is working and there's no reason it shouldn't work for App2 as well.

Suspect either you have a load balancer issue or App2 is not configured for session replication ("distributable" element in web.xml).