The IIS setting (at least in 6.0) applies only to Classic ASP, not ASP.NET.
When IIS recycles your app (which can occur many times during the day
depending on memory pressure and ISS settings for same), your InProc sessions
will go away.
Normally there is no need to set such a long Session Timeout as it has a
sliding expiration that "renews" the timeout whenever there is a request for
a page. In addition, it can pose a real security risk. The best thing to do
is not rely on Session at all, depending on what your needs are.
Finally, this is the C# language group - your post really belongs at the
ASP.NET group - it is not language specific but more about which framework.
-- Peter
Recursion: see Recursion
site:
http://www.eggheadcafe.com
unBlog:
http://petesbloggerama.blogspot.com
BlogMetaFinder:
http://www.blogmetafinder.com
"fi**********@gmail.com" wrote:
Hi,
I had created a web application where Session expiry was set to 2,000
minutes in IIS. in web config i had given like this
<sessionState timeout="2,000" mode="InProc"></sessionStatebut MY web
application was left logged in at 18:00 15th Oct, but on the following
day 08:30 16th Oct, the session expired as soon as MY web application
was used. It was also noted that during the day, MY web application
occasionally got session expiry when it was constantly being used.Does
the session expiry need to be set up anywhere else? There are no
Error logs created.
Will you please help me to resolve this issue. i expect your reply
soon .
With Thanks
Fijo Francis T