Prev: sending mail with images
Next: Error: File /trxweb/trxweb.asp Unexpected error.(E06D7363)
From: anon on 27 Feb 2007 10:51
In our application we need to increase the session timeout to 2 hours when
the user requests a certain page.
We use the following code to do that.
Session.Timeout = 120
This works fine on IIS 5.0.
After we moved the application to IIS 6.0 the session timeout does increase
when the page in executed. It logs the user out after 20 mins which is the
default.
Is there any setting on IIS 6.0 which we need to change ?

Thanks for your help.

From: Anthony Jones on 27 Feb 2007 17:46

"anon" <anon(a)discussions.microsoft.com> wrote in message
news:BDCB804B-9BA5-460C-B484-AA898716CB95(a)microsoft.com...
> In our application we need to increase the session timeout to 2 hours when
> the user requests a certain page.
> We use the following code to do that.
> Session.Timeout = 120
> This works fine on IIS 5.0.
> After we moved the application to IIS 6.0 the session timeout does
increase
> when the page in executed. It logs the user out after 20 mins which is the
> default.
> Is there any setting on IIS 6.0 which we need to change ?
>
> Thanks for your help.
>

By default an application pool will be configured to shutdown after 20
minutes if it has been idle. To absolutely sure that the user gets the full
allotted period of timeout this value needs to be the same or larger than
the session timeout.

You can find it by first checking which application pool your application is
assigned to in the application folders propeties home directory tab
(probably DefaultAppPool).

The open the properties of the pool. On the performance tab change the idle
timeout.



From: anon on 27 Feb 2007 18:53
Thanks for your response. Will try what you suggested.
From: Dave Anderson on 27 Feb 2007 20:10
Anthony Jones wrote:
> By default an application pool will be configured to
> shutdown after 20 minutes if it has been idle.

Goodness! I have plenty of ASP experience, but would never have looked for
session limit problems in the application pool if I had not read this.

Of course, my servers all get 24/7 usage, so this would have been unlikely
to affect me, but still...



--
Dave Anderson

Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms.


 | 
Pages: 1
Prev: sending mail with images
Next: Error: File /trxweb/trxweb.asp Unexpected error.(E06D7363)