Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Chrome confused with session timeout/restart
#7
Hi there.  More information for you Alexandre.  The issue in the architecture when an expired session is attempted to be touched is really seen when the machine is left overnight and then that system just hangs in the old session ID with that document information I already sent.  I got rid of the lag for the new session creation by setting the RestartExpiredSession Flag to true and then putting session FreeInstance/create code in the the OnSessionRestarted event.  If I set only the RestartExpiredSession flag then I was seeing the same issue.

Hopefully this assists you to trace the issue in the architecture.  I am able to get into the session restart process so at least I eliminated that issue.  So to summarize, when the session is expired and machine left overnight, then when any server function is touched, the system hangs waiting.  The issue is in Opera now too but at least Firefox still seems OK.  Maybe this is a canary to a larger issue that more and more people will find as the whatever is different in the browser is seen more and more?

If I find anything else that I can add to this issue, I will let you know but I have hit a wall on what I can do from here on the first part since ANY server operation just hangs waiting for the session so nothing I can do.  The issue is also dependent on what is in the session too on length of time.  If I time out the session before I log into the system, then the time to get a new session is less time.  The key factors in my experiments are length of time the machine is left alone and size of the session.

Cheers.
Reply


Messages In This Thread
RE: Chrome confused with session timeout/restart - by bob9999 - 03-16-2020, 04:22 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)