Setup:
- global.asa
- Contains Session_Start event which checks to see if the user
has a cookie...if so, connect to the database and load their
settings into Session from the database.
- login.asp
- Writes a cookie and loads user settings into Session from the
database. (They will not go to login.asp each visit to the site.
After they are authenticated the cookie will prevent forcing login for
24 hrs.)
The problem we are having is that after the user has logged in and has
a valid cookie, an exception may trigger the recycling of a worker
process causing them to recieve a new session. At this point, it
appears that the Session_Start event is not firing because the cookie
is available and the user settings are not being loaded into Session.
It is as if the Session_Start event does not fire in each worker
process.
We know that the Session_Start event works because if we open a new
instance of IE while the user has the cookie, theie settings are
loaded and they are able to use the application. This was working
fine for years with IIS 5 and works with IIS 6 and only one worker
process.
NOTE: We DO NOT need to share session information across worker
processes as I know this will not work and is unnecessary since
settings "should" be loaded for each session in each process
separately using the Session_Start event.
Any ideas?
Thanks