Classic ASP session timeout under IIS6.0

[P. Glassel]

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.

 

[P. Glassel]

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.

 

[Ray at]

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

 

[P. Glassel]

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

 

[P. Glassel]

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-----


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!)

I see ye are in pain, Most Tender Newbie, so as to yere punishment for
posting, accept yere lashings, walk the gangplank, drink ye Olde
Starbucke's and go see David Wang's contribution to the last thread at
http://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_umsgid=&lr
=&as_drrb=q&as_qdr=&as_mind=12&as_minm=5&as_miny=1981&as_m
axd=28&as_maxm=7&as_maxy=2003&safe=images
which is significant enough to paste here:

w> I think you're observing the application "idle" recycling happening
in 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 do
not
w> make another request to that application within 15 minutes, that
application
w> is going to recycle and remove itself from memory, losing any session
state,
w> app state, etc -- everything -- that is not otherwise persisted
(there are
w> ASP-based session state products that would overcome this as well as
provide
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 timeout
of Y.
w> If you make one request at time 0 and another at time between Y and
X,
w> session state will look lost.
w> 2. Your ASP app does not expect any

isolation/recycling/idle timeout

 

[Michael D. Kersey]

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