views:

21

answers:

0

I am working with an web application that has its sessions timing out a lot quicker than expected. We expected a timeout of 15 minutes but it's timing out at 3-4 minutes. Info about environment:

  • IIS6
  • classic ASP / COM+ app
  • timeout OK on current PROD, much quicker in dev / QA environments
  • We already disabled app pool recycling, and even put IIS in isolation mode - no effect
  • HTTP err log doesn't display any lines when session times out

We've done a close comparison of PROD and DEV / QA environments, and given we use virtual machines on all of them, settings should be preserved. I tried to find IIS blog notes from David Wang but many of them now have HTTP 404 errors, and I don't know what else to do. Please help!

At the very least, is there a way to get IIS to log every time a session expires? At the very least some means of logging / debugging IIS would be useful. Thanks in advance.