Are you saying that when you fail over you have to log in again? Are you using container-managed FORM authentication? If so, the problem is the information to reauthenticate the user following failover is not replicated as part of the session. See http://jira.jboss.com/jira/browse/JBAS-1900
Both nodes I'm using stay up. Could it be a case of:
Login on node1
Switch to node2
Logon needed for node2 (info not replicated)
and so on?
How would I check if I am using FORM authentication?
Thanks very much,
I tried it out where it logs in using node1, returns to the login screen (still on node1) and just keeps returning to the login screen. If I press the login button loads of times in a row it will eventually log in and from there on out everything behaves as expected ie if the node fails it'll switch without having to login again.
You're using container managed FORM authentication if you have login-config element in web.xml that specifies FORM. If that's not what you're using, then you must have your own login code. In that case you'd need to take a look in a debugger to see what is going on.
Thanks very much for that. The solution was that the sessionID is compared with a stored ID to see if you're logged in. The nodes were appending their name to the end of the id essentially creating a unique id for each node causing the login page to keep redirecting to itself.
Hey gerMonday - You indicated you found a solution but from your post I can't tell what you did to fix it. How did you prevent the node from being appended to the sessionID?