Wrox Programmer Forums
| Search | Today's Posts | Mark Forums Read
ASP.NET 1.0 and 1.1 Professional For advanced ASP.NET 1.x coders. Beginning-level questions will be redirected to other forums. NOT for "classic" ASP 3 or the newer ASP.NET 2.0 and 3.5
Welcome to the p2p.wrox.com Forums.

You are currently viewing the ASP.NET 1.0 and 1.1 Professional section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old June 22nd, 2007, 02:12 PM
Authorized User
 
Join Date: Nov 2005
Location: , , .
Posts: 15
Thanks: 1
Thanked 0 Times in 0 Posts
Default Session/Cookie Expires, Login page appears

we have few websites (each site for each client--uses same asp.net code but each site uses a different database), which is running (load balanced) across diff web servers. in few sites, when users were working in web site (any page) automatically they were redirected to login page when clicking links/buttons,etc. happens across sites/servers. once logged again, they are fine for few mins or hrs till it reoccurs.

what i need to look to fix this session or cookie expires problem? i checked iis logs it didnt give much info.

please help, thanks in advance.
 
Old June 25th, 2007, 06:03 AM
planoie's Avatar
Friend of Wrox
Points: 16,481, Level: 55
Points: 16,481, Level: 55 Points: 16,481, Level: 55 Points: 16,481, Level: 55
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Aug 2003
Location: Clifton Park, New York, USA.
Posts: 5,407
Thanks: 0
Thanked 16 Times in 16 Posts
Default

How are you persisting the user's login information? In a cookie or in session?

If it's in the cookie, then I'm not sure what the problem could be. The cookie will be sent to any browser in the web farm so that shouldn't cause a problem.

If you are using session then what type of session management are you using? If you are using In-Proc than it is likely that your users are getting bumped from one server to another and thus their session data is not there on the other server. You can use SQL bases session state to eliminate this problem.

-Peter
 
Old June 26th, 2007, 08:36 PM
Authorized User
 
Join Date: Nov 2005
Location: , , .
Posts: 15
Thanks: 1
Thanked 0 Times in 0 Posts
Default

thanks, we use cookie to store user info.

but also we use inproc for sessionstate, but if we change to sql base, what are the disadvantages? any performance issues?

 
Old June 27th, 2007, 06:19 AM
planoie's Avatar
Friend of Wrox
Points: 16,481, Level: 55
Points: 16,481, Level: 55 Points: 16,481, Level: 55 Points: 16,481, Level: 55
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Aug 2003
Location: Clifton Park, New York, USA.
Posts: 5,407
Thanks: 0
Thanked 16 Times in 16 Posts
Default

In process will always be faster. Will you notice the difference? Probably not. I have used SQL server session state and can't say I notice the difference. Your load balancer slows down the application too, but some small amount, but you probably don't notice that.

Typically, what slows down your application is the application itself. The performance difference using SQL session is negligible and necessary in order for the application to be scalable.

-Peter




Similar Threads
Thread Thread Starter Forum Replies Last Post
Reporting Services Login box appears zulf BOOK: Professional SQL Server 2005 Reporting Services ISBN: 0-7645-8497-9 6 August 30th, 2011 06:16 AM
login page. cookie handling. richie86 ASP.NET 1.0 and 1.1 Basics 1 November 27th, 2005 05:13 AM
How to write a cookie during a login session taoree ASP.NET 1.0 and 1.1 Basics 3 April 18th, 2004 02:40 PM
login page and session variables scdownload Classic ASP Basics 0 December 8th, 2003 06:13 PM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.