AM without session failover set up?

Generally I have at least 2 servers for redundancy and plan 2 servers to host AM behind a load balancer. Unfortunately I am unable to support message queue and berkeley sleepycat DB which is required for session failover. So I am curious what the session behavior is without the session failover set up. When one AM server goes down and the other is used does the user click on a link and is asked to login again? Wondering how graceful it is.

[450 byte] By [Xoth] at [2007-11-26 10:00:06]
# 1

Hi.

I have been kind of struggling with session failover for sometime now (it worked perfectly with 2003Q4 though).

Once you have a session queue / DB established, this is how things proceed:

1. User hits load balancer, which directs him / her to one of the servers.

2. User logs in. Load balancer maintains a sticky session. Future requests go to the same server.

3. Say that server goes down. User clicks. Load balancer figures out that server is down, redirects user to another AM server.

4. If you have session failover in place, user can continue to work without logging in (technically!).

It was seamless with 2003Q4. We pulled the cable on one AM server (so resulting DS, DPS, AM and message broker all went offline), and still the user's session transitioned to the other server.

If you do get session failover to work with 2005Q4, would be grateful if you could post something about it.

ankushkapoor at 2007-7-7 1:28:24 > top of Java-index,Web & Directory Servers,Directory Servers...
# 2

Did you get to implement this successfully? Sincerely any insight that you could share with reference to session failover. I keep getting a Null pointer exception in amSession (debug file) with logging set to message when I implement session failover. It seems AM (2005Q4) is not able to save / delete sessions. Am baffled with the why though.

Thanks for the help.

ankushkapoor at 2007-7-7 1:28:24 > top of Java-index,Web & Directory Servers,Directory Servers...
# 3
Sorry cant be of help. My note was about not implementing session failover and what the user experiences.
Xoth at 2007-7-7 1:28:24 > top of Java-index,Web & Directory Servers,Directory Servers...