By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
429,214 Members | 2,066 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 429,214 IT Pros & Developers. It's quick & easy.

Classic ASP session timeout under IIS6.0

P: n/a
I'm having problems getting session timeouts to change
programmaticlaly under IIS6.0. This is unchanged code
that ran as expected under IIS5.0.

Anyone else run into this problem?

Thx.
Jul 19 '05 #1
Share this Question
Share on Google+
8 Replies


P: n/a
you mean they aren't timing out?
Code samples please

--
----------------------------------------------------------
Curt Christianson (Software_AT_Darkfalz.Com)
Owner/Lead Designer, DF-Software
http://www.Darkfalz.com
---------------------------------------------------------
...Offering free scripts & code snippits for everyone...
---------------------------------------------------------

"P. Glassel" <pg******@prga.com> wrote in message
news:01****************************@phx.gbl...
I'm having problems getting session timeouts to change
programmaticlaly under IIS6.0. This is unchanged code
that ran as expected under IIS5.0.

Anyone else run into this problem?

Thx.

Jul 19 '05 #2

P: n/a
not certain why you would have this problem. Only thing I could think of is
that the IIS config settings are overriding yours. Try adjusting them from
the IIS manager once as a test.
--
----------------------------------------------------------
Curt Christianson (Software_AT_Darkfalz.Com)
Owner/Lead Designer, DF-Software
http://www.Darkfalz.com
---------------------------------------------------------
...Offering free scripts & code snippits for everyone...
---------------------------------------------------------

"P. Glassel" <pg******@prga.com> wrote in message
news:01****************************@phx.gbl...
No, I mean the timeout is not changing. They continue to
timeout in 20 minutes regardless of what the new settings
are.

Example couldn't be simpler.

After validating a login request the timeout is extended
as follows:

session.Timeout=60

This worked just fine under IIS5.0/Windows 2000 server
and fails to work under IIS6.0/Windows 2003.

Phil

-----Original Message-----
you mean they aren't timing out?
Code samples please

--
---------------------------------------------------------

-
Curt Christianson (Software_AT_Darkfalz.Com)
Owner/Lead Designer, DF-Software
http://www.Darkfalz.com
---------------------------------------------------------
...Offering free scripts & code snippits for everyone...
---------------------------------------------------------

"P. Glassel" <pg******@prga.com> wrote in message
news:01****************************@phx.gbl...
I'm having problems getting session timeouts to change
programmaticlaly under IIS6.0. This is unchanged code
that ran as expected under IIS5.0.

Anyone else run into this problem?

Thx.

.

Jul 19 '05 #3

P: n/a
Something's odd here. The IIS manager doesn't seem to
affect the settings either. I wonder where the IIS6.0 ASP
interpreter is getting its settings from? MS seems to be
a little confused about session workings in ASP vs ASPX
in some areas... or possibly I am.
-----Original Message-----
not certain why you would have this problem. Only thing I could think of isthat the IIS config settings are overriding yours. Try adjusting them fromthe IIS manager once as a test.
--
--------------------------------------------------------- -Curt Christianson (Software_AT_Darkfalz.Com)
Owner/Lead Designer, DF-Software
http://www.Darkfalz.com
---------------------------------------------------------
...Offering free scripts & code snippits for everyone...
---------------------------------------------------------

"P. Glassel" <pg******@prga.com> wrote in message
news:01****************************@phx.gbl...
No, I mean the timeout is not changing. They continue to timeout in 20 minutes regardless of what the new settings are.

Example couldn't be simpler.

After validating a login request the timeout is extended as follows:

session.Timeout=60

This worked just fine under IIS5.0/Windows 2000 server
and fails to work under IIS6.0/Windows 2003.

Phil

>-----Original Message-----
>you mean they aren't timing out?
>Code samples please
>
>--
>------------------------------------------------------ ---
-
>Curt Christianson (Software_AT_Darkfalz.Com)
>Owner/Lead Designer, DF-Software
>http://www.Darkfalz.com
>------------------------------------------------------

--- >...Offering free scripts & code snippits for everyone... >------------------------------------------------------ --- >
>"P. Glassel" <pg******@prga.com> wrote in message
>news:01****************************@phx.gbl...
>> I'm having problems getting session timeouts to change >> programmaticlaly under IIS6.0. This is unchanged code >> that ran as expected under IIS5.0.
>>
>> Anyone else run into this problem?
>>
>> Thx.
>
>
>.
>

.

Jul 19 '05 #4

P: n/a
If you have ASP and ASPX setup it may be looking for the web.config which
has a session timeout setting as well....

--
----------------------------------------------------------
Curt Christianson (Software_AT_Darkfalz.Com)
Owner/Lead Designer, DF-Software
http://www.Darkfalz.com
---------------------------------------------------------
...Offering free scripts & code snippits for everyone...
---------------------------------------------------------

"P. Glassel" <pg******@prga.com> wrote in message
news:01****************************@phx.gbl...
Something's odd here. The IIS manager doesn't seem to
affect the settings either. I wonder where the IIS6.0 ASP
interpreter is getting its settings from? MS seems to be
a little confused about session workings in ASP vs ASPX
in some areas... or possibly I am.
-----Original Message-----
not certain why you would have this problem. Only thing

I could think of is
that the IIS config settings are overriding yours. Try

adjusting them from
the IIS manager once as a test.
--
---------------------------------------------------------

-
Curt Christianson (Software_AT_Darkfalz.Com)
Owner/Lead Designer, DF-Software
http://www.Darkfalz.com
---------------------------------------------------------
...Offering free scripts & code snippits for everyone...
---------------------------------------------------------

"P. Glassel" <pg******@prga.com> wrote in message
news:01****************************@phx.gbl...
No, I mean the timeout is not changing. They continue to timeout in 20 minutes regardless of what the new settings are.

Example couldn't be simpler.

After validating a login request the timeout is extended as follows:

session.Timeout=60

This worked just fine under IIS5.0/Windows 2000 server
and fails to work under IIS6.0/Windows 2003.

Phil


>-----Original Message-----
>you mean they aren't timing out?
>Code samples please
>
>--
>------------------------------------------------------ --- -
>Curt Christianson (Software_AT_Darkfalz.Com)
>Owner/Lead Designer, DF-Software
>http://www.Darkfalz.com
>------------------------------------------------------ --- >...Offering free scripts & code snippits for everyone... >------------------------------------------------------ --- >
>"P. Glassel" <pg******@prga.com> wrote in message
>news:01****************************@phx.gbl...
>> I'm having problems getting session timeouts to change >> programmaticlaly under IIS6.0. This is unchanged code >> that ran as expected under IIS5.0.
>>
>> Anyone else run into this problem?
>>
>> Thx.
>
>
>.
>

.

Jul 19 '05 #5

P: n/a
I haven't really been following this thread, but the "it's probably a bug"
caught my eye. 99 times out of 100, it is not a bug; it's a user error of
some sort. Are you sure that you aren't switching applications and then not
seeing your session vars becaue of it or something along those lines? Or
are you initiating new iexplore.exe processes by opening new browser windows
with your client-side code?

Ray at home

--
Will trade ASP help for SQL Server help
"P. Glassel" <pg******@prga.com> wrote in message
news:02****************************@phx.gbl...
Well, changing the settings in the web.config didn't help
either. I guess MS simply has yet another bug here. There
are a host of other bugs in their interpreter, so it is
clear that this is an extensive rewrite of the classic
ASP interpreter issued with IIS5.0.

All the bugs make it very difficult to deal with. The
good news is that its execution is substantially faster
than under IIS5.0 giving much faster response to complex
pages. I suspect they borrowed their JIT techology from
the .NET part of the system.

Phil
-----Ori

Jul 19 '05 #6

P: n/a
Ray, you really need to follow the thread before you
reply with a comment like this. I am a professional and
am lothe to go to a newsgroup for exactly this reason. If
you think ASP under IIS6.0 is not buggy, you haven't used
it.

Phil
-----Original Message-----
I haven't really been following this thread, but the "it's probably a bug"caught my eye. 99 times out of 100, it is not a bug; it's a user error ofsome sort. Are you sure that you aren't switching applications and then notseeing your session vars becaue of it or something along those lines? Orare you initiating new iexplore.exe processes by opening new browser windowswith your client-side code?

Ray at home

--
Will trade ASP help for SQL Server help
"P. Glassel" <pg******@prga.com> wrote in message
news:02****************************@phx.gbl...
Well, changing the settings in the web.config didn't help either. I guess MS simply has yet another bug here. There are a host of other bugs in their interpreter, so it is
clear that this is an extensive rewrite of the classic
ASP interpreter issued with IIS5.0.

All the bugs make it very difficult to deal with. The
good news is that its execution is substantially faster
than under IIS5.0 giving much faster response to complex pages. I suspect they borrowed their JIT techology from
the .NET part of the system.

Phil
>-----Ori

.

Jul 19 '05 #7

P: n/a
I guess you didn't read the thread either. No variables
are being lost, oh wise one!

I also never said I didn't write code with bugs, I only
said MS has more than their fair share.

I am wasting my time here!

Sorry I asked.
-----Original Message-----
"P. Glassel" wrote:
Ray, you really need to follow the thread before you
reply with a comment like this. I am a professional and
am lothe to go to a newsgroup for exactly this reason. If you think ASP under IIS6.0 is not buggy, you haven't used it.
Har, har, har! A *professional* who apparently
- writes code w/o bugs and
- "is lothe(sic) to go to a newsgroup"
Very funny, made me day!8-))

I see ye are in pain, Most Tender Newbie, so as to yere

punishment forposting, accept yere lashings, walk the gangplank, drink ye OldeStarbucke's and go see David Wang's contribution to the last thread athttp://www.google.com/groups? as_q=session.timeout&num=20&as_scoring=r&hl=en&ie= ISO-
8859-
1&btnG=Google+Search&as_epq=iis+6&as_oq=&as_eq=&as _ugroup=
microsoft.public.*&as_usubject=&as_uauthors=&as_um sgid=&lr
=&as_drrb=q&as_qdr=&as_mind=12&as_minm=5&as_miny=1 981&as_m
axd=28&as_maxm=7&as_maxy=2003&safe=imageswhich is significant enough to paste here:

w> I think you're observing the application "idle" recycling happeningin the
w> back ground, which resets all state that is not otherwise persisted.By
w> default, if you make a request to some application of IIS, if you donot
w> make another request to that application within 15 minutes, thatapplication
w> is going to recycle and remove itself from memory, losing any sessionstate,
w> app state, etc -- everything -- that is not otherwise persisted(there are
w> ASP-based session state products that would overcome this as well asprovide
w> scale-out abilities).
w>
w> Situations where you'll see this sort of "disappearing variables"behavior
w> from ASP are:
w> 1. Your ASP Session timeout of X is greater than the IIS idle timeoutof Y.
w> If you make one request at time 0 and another at time between Y andX,
w> session state will look lost.
w> 2. Your ASP app does not expect any isolation/recycling/idle timeoutof Y.
w> In this case, if you make one request at time 0 and another at time >Y,
w> state would look lost.
w>
w> How do you deal with this?
w> 1. Use ASP Session State products that persist state beyond thelifetime of
w> a process
w> 2. Make sure that the idle timeout is greater than all your othertimeouts
w> 3. Make sure to tune all other health monitoring parametersapproriately
w> since they also recycle processes.
w> --
w> //David

Also see "Demonstration of Application Pool recycling side affects onIIS 6" at
http://www.iisfaq.com/default.aspx?View=A560&P=1

and "Application Pool settings...":
http://msdn.microsoft.com/library/default.asp? url=/library/en-
us/cpguide/html/cpconapplicationpoolsettingsforworkerproce
ssisolationmode.asp
Aaargh, avast ye mates,
Michael D. Kersey
XML pirate of the good ship Perl
.

Jul 19 '05 #8

P: n/a
"P. Glassel" wrote:

I guess you didn't read the thread either. Aaaarrrgh! Wrong, Newbie! I've read it 3 times already! Ye're wastin'
our time!
No variables
are being lost, oh wise one! Aaaarrrgh! How exactly are you determining if/when the session times
out? Methinks ye're lookin' at somethin' and thinkin' it's somethin'
else.
I also never said I didn't write code with bugs, I only
said MS has more than their fair share.

I am wasting my time here! Aaaarrrgh! Only because ye aren't tellin' us *all* the truth matey! Ye
better post some code other than "Session.Timeout = 60" to get a
diagnosis, otherwise we'll conclude ye're a professional idiot and
keelhaul ye. He he, or worse, belittle ye in front of yere friends!-)
Sorry I asked.


Aaaarrrgh! Belay that talk, Newbie! Ye're taxin' our patience. Now ye
must answer the 3 magic questions; if you answer wrong we get to flog
keelhaul ya:
I. We don't see no parrot on yere shoulder: where is yere parrot?
II. What exactly makes ye think that the timeout ain't changin'?
III. Why are ye lookin' at the cabin boy's arse that way? Beware ye make
the Captain jealous.

Aaarrrgh!
Michael D. Kersey
XML pirate of the good ship Perl
Jul 19 '05 #9

This discussion thread is closed

Replies have been disabled for this discussion.