We have 2 web servers (IIS) setup with Windows 2003 NLB and sticky sessions. When one server drops out, the active connections will move to the active server. Is it possible to detect this failover for new reqeusts and force the request to be redirected to another page?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Failover is working well. I'm interested in custom actions after failover occurs. I'd like all initial requests to a given server redirect to a specific page (similar to a login page).
Ex) If a user has been working in server A and then gets redirected to B because A drops out, I would like B to force them to a new page and not server the page requested by the user.
The failover will interrupt the normal user experience.
Yes, this does go against the failover/high availability pros of a cluster. The primary reason for our cluster is to distribute load and not provide 100% uptime though. With sticky sessions, we don't expect users to switch web servers at all.
The application has a lot of important data in asp.net session. If the user gets in a scenario where they get bounced back and forth between web servers causing multiple active sessions, they could CRUD wrong records after the switch. We can't get to a state server or db session server in the near future. So, a simple solution would have been to redirect them to a place that cleared out users' sessions after web server switches. Your coding suggestion will work, but I was hoping there might be some nlb configuration option.
Business Accounts
Answer for Membership
by: cj_1969Posted on 2009-07-23 at 04:08:57ID: 24923723
Its a cluster, it should be doing this automatically.
If it is not then this would imply that the cluster is not configured correctly or that the problem is on the backend heart-beat connection and not with the network access to the cluster itself.
Can you describe the situation a little more.
What is happening when one of the servers is "dropping out"?