IIS 6.0 asp Session problem

Is it always 120 seconds?

Unexpected loss of server variables usually means the worker process exited
for some reason (expected or unexpected), causing ASP to lose state (the
other reason would be an ASP bug). A worker process exit/crash usually have
an event log message associated with it if it was not expected by IIS. On
the other hand, a configured worker process recycle would be an example of
an expected worker process exit when it triggers.

I cannot reproduce the claimed session problem with my test Session ASP
page. I have a page which uses the querystring to add a test session
variable. I added a couple, then waited 3 minutes, and made another request
using the same session to add another session variable -- and I saw that the
previous variables still existed (so I definitely have an ASP page which
kept session state > 120 seconds on IIS6).

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Stefano Cecconi" <webmaster.RemoveThis@technet.it> wrote in message
news:eZe5vm8dDHA.828@TK2MSFTNGP11.phx.gbl...
Hi,

i have a problem with asp sessions : they expire after 120 seconds even if i
have 20 minutes in my settings.

I know i could use aspnet_state, but it doesn't solve the problem for normal
asp pages.

http://62.149.130.111/sessione.asp

I have a recycle every 120 minutes, http connection timeout 900 seconds,
session timeout 20 minutes.

The problem is the same on several servers.

Any idea?

Stefano
 >> Stay informed about: IIS 6.0 asp Session problem 

Its not always 120 sec with us its at random times but it always seems to
happen before the set idle time is reached

We are seeing a ton of these warnings assuming 0x80 could be the idle
timeout?
A process serving application pool 'xxxxxxxxxx' terminated unexpectedly. The
process id was '4944'. The process exit code was '0x80'. which sometimes
lead to this

Application pool 'xxxxxxxxxxxxx' is being automatically disabled due to a
series of failures in the process(es) serving that application pool.

Im assuming the latter is being caused by many of the previous errors

Can we keep you informed of this to hopefully trace the problem?

One other question. Im assuming with application pools if say you had 100
sites and 1 application pool that would use less memory than 100 sites split
into 10 application pools?

Thanks

Robbie

"David Wang [Msft]" <someone DeleteThis @online.microsoft.com> wrote in message
news:OqhjNpBeDHA.2428@TK2MSFTNGP09.phx.gbl...
 > Is it always 120 seconds?
 >
 > Unexpected loss of server variables usually means the worker process
exited
 > for some reason (expected or unexpected), causing ASP to lose state (the
 > other reason would be an ASP bug). A worker process exit/crash usually
have
 > an event log message associated with it if it was not expected by IIS. On
 > the other hand, a configured worker process recycle would be an example of
 > an expected worker process exit when it triggers.
 >
 > I cannot reproduce the claimed session problem with my test Session ASP
 > page. I have a page which uses the querystring to add a test session
 > variable. I added a couple, then waited 3 minutes, and made another
request
 > using the same session to add another session variable -- and I saw that
the
 > previous variables still existed (so I definitely have an ASP page which
 > kept session state > 120 seconds on IIS6).
 >
 > --
 > //David
 > IIS
 > This posting is provided "AS IS" with no warranties, and confers no
rights.
 > //
 > "Stefano Cecconi" <webmaster DeleteThis @technet.it> wrote in message
 > news:eZe5vm8dDHA.828@TK2MSFTNGP11.phx.gbl...
 > Hi,
 >
 > i have a problem with asp sessions : they expire after 120 seconds even if
i
 > have 20 minutes in my settings.
 >
 > I know i could use aspnet_state, but it doesn't solve the problem for
normal
 > asp pages.
 >
<font color=purple> > <a style='text-decoration: underline;' href="http://62.149.130.111/sessione.asp</font" target="_blank">http://62.149.130.111/sessione.asp</font</a>>
 >
 > I have a recycle every 120 minutes, http connection timeout 900 seconds,
 > session timeout 20 minutes.
 >
 > The problem is the same on several servers.
 >
 > Any idea?
 >
 > Stefano
 >
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: IIS 6.0 asp Session problem 

Ok. In that case, it really isn't an ASP session problem but rather a known
generic problem between ASP state and Worker Process recycling.

Namely, ASP stores state in the process it runs in, and if that process
recycles for whatever reason (i.e. worker process crashed when running 3rd
party/custom code, worker process recycles normally due to configuration,
etc), that state is lost.

What you are seeing in the event log is evidence of the former. Something
that was running in the application pool crashed, bringing down the worker
process and hence any ASP state that was contained in that process. A rapid
failure of worker process leads to the AppPool being disabled and 503s
returned.

So, your session problem is really an indication of something else that's
going wrong on your system. With prior versions of IIS, this probably would
have brought down your server -- with IIS6, it kept going, but you noticed
the state loss. I would suggest you troubleshoot what is crashing -- look
at IIS State: <a style='text-decoration: underline;' href="http://www.iisfaq.com/default.aspx?view=P197" target="_blank">http://www.iisfaq.com/default.aspx?view=P197</a>

Thus, you can see that ASP.Net, with its session state service, is immune to
this problem -- code can bring down ASP.Net applications, but IIS6 will just
spin up another worker process, which retrieves its state from the session
state service, and it's right back where it left off.

Here is how to think about application pools/isolation/memory consumption --
assume each website takes 1 MB of memory and each application pool takes 1MB
of memory. 100 applications in one app pool takes 101 MB of memory.
However, if any of the 100 applications crash, it loses state for the other
99. Meanwhile, if you have 10 applications in 10 app pools, you use up 110
MB of memory, but if any of the applications crash, it loses state for 9
others, not 99. So, you spend 9% more memory to bring isolation to 9% of
applications. If you isolate each application in its own app pool, you
spend 100% more memory to bring total isolation to 100% apps.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Robbie Wallis" <robbie.wallis DeleteThis @virgin.net> wrote in message
news:%231TNlMDeDHA.2428@TK2MSFTNGP09.phx.gbl...
Its not always 120 sec with us its at random times but it always seems to
happen before the set idle time is reached

We are seeing a ton of these warnings assuming 0x80 could be the idle
timeout?
A process serving application pool 'xxxxxxxxxx' terminated unexpectedly. The
process id was '4944'. The process exit code was '0x80'. which sometimes
lead to this

Application pool 'xxxxxxxxxxxxx' is being automatically disabled due to a
series of failures in the process(es) serving that application pool.

Im assuming the latter is being caused by many of the previous errors

Can we keep you informed of this to hopefully trace the problem?

One other question. Im assuming with application pools if say you had 100
sites and 1 application pool that would use less memory than 100 sites split
into 10 application pools?

Thanks

Robbie

"David Wang [Msft]" <someone DeleteThis @online.microsoft.com> wrote in message
news:OqhjNpBeDHA.2428@TK2MSFTNGP09.phx.gbl...
 > Is it always 120 seconds?
 >
 > Unexpected loss of server variables usually means the worker process
exited
 > for some reason (expected or unexpected), causing ASP to lose state (the
 > other reason would be an ASP bug). A worker process exit/crash usually
have
 > an event log message associated with it if it was not expected by IIS. On
 > the other hand, a configured worker process recycle would be an example of
 > an expected worker process exit when it triggers.
 >
 > I cannot reproduce the claimed session problem with my test Session ASP
 > page. I have a page which uses the querystring to add a test session
 > variable. I added a couple, then waited 3 minutes, and made another
request
 > using the same session to add another session variable -- and I saw that
the
 > previous variables still existed (so I definitely have an ASP page which
 > kept session state > 120 seconds on IIS6).
 >
 > --
 > //David
 > IIS
 > This posting is provided "AS IS" with no warranties, and confers no
rights.
 > //
 > "Stefano Cecconi" <webmaster DeleteThis @technet.it> wrote in message
 > news:eZe5vm8dDHA.828@TK2MSFTNGP11.phx.gbl...
 > Hi,
 >
 > i have a problem with asp sessions : they expire after 120 seconds even if
i
 > have 20 minutes in my settings.
 >
 > I know i could use aspnet_state, but it doesn't solve the problem for
normal
 > asp pages.
 >
<font color=purple> > <a style='text-decoration: underline;' href="http://62.149.130.111/sessione.asp</font" target="_blank">http://62.149.130.111/sessione.asp</font</a>>
 >
 > I have a recycle every 120 minutes, http connection timeout 900 seconds,
 > session timeout 20 minutes.
 >
 > The problem is the same on several servers.
 >
 > Any idea?
 >
 > Stefano
 >
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: IIS 6.0 asp Session problem 

I found the cause :

disabling the recycle "after consuming too much memory" sessions work fine.

The strange thing is that my setting was to recycle at 500Mb, and the worker
process never reached this value, but it was recycling every 120 seconds...

A bug?

Stefano

"Robbie Wallis" <robbie.wallis DeleteThis @virgin.net> ha scritto nel messaggio
news:%231TNlMDeDHA.2428@TK2MSFTNGP09.phx.gbl...
 > Its not always 120 sec with us its at random times but it always seems to
 > happen before the set idle time is reached
 >
 > We are seeing a ton of these warnings assuming 0x80 could be the idle
 > timeout?
 > A process serving application pool 'xxxxxxxxxx' terminated unexpectedly.
The
 > process id was '4944'. The process exit code was '0x80'. which sometimes
 > lead to this
 >
 > Application pool 'xxxxxxxxxxxxx' is being automatically disabled due to a
 > series of failures in the process(es) serving that application pool.
 >
 > Im assuming the latter is being caused by many of the previous errors
 >
 > Can we keep you informed of this to hopefully trace the problem?
 >
 > One other question. Im assuming with application pools if say you had 100
 > sites and 1 application pool that would use less memory than 100 sites
split
 > into 10 application pools?
 >
 > Thanks
 >
 > Robbie
 >
 > "David Wang [Msft]" <someone DeleteThis @online.microsoft.com> wrote in message
 > news:OqhjNpBeDHA.2428@TK2MSFTNGP09.phx.gbl...
  > > Is it always 120 seconds?
  > >
  > > Unexpected loss of server variables usually means the worker process
 > exited
  > > for some reason (expected or unexpected), causing ASP to lose state (the
  > > other reason would be an ASP bug). A worker process exit/crash usually
 > have
  > > an event log message associated with it if it was not expected by IIS.
On
  > > the other hand, a configured worker process recycle would be an example
of
  > > an expected worker process exit when it triggers.
  > >
  > > I cannot reproduce the claimed session problem with my test Session ASP
  > > page. I have a page which uses the querystring to add a test session
  > > variable. I added a couple, then waited 3 minutes, and made another
 > request
  > > using the same session to add another session variable -- and I saw that
 > the
  > > previous variables still existed (so I definitely have an ASP page which
  > > kept session state > 120 seconds on IIS6).
  > >
  > > --
  > > //David
  > > IIS
  > > This posting is provided "AS IS" with no warranties, and confers no
 > rights.
  > > //
  > > "Stefano Cecconi" <webmaster DeleteThis @technet.it> wrote in message
  > > news:eZe5vm8dDHA.828@TK2MSFTNGP11.phx.gbl...
  > > Hi,
  > >
  > > i have a problem with asp sessions : they expire after 120 seconds even
if
 > i
  > > have 20 minutes in my settings.
  > >
  > > I know i could use aspnet_state, but it doesn't solve the problem for
 > normal
  > > asp pages.
  > >
<font color=green>  > > <a style='text-decoration: underline;' href="http://62.149.130.111/sessione.asp</font" target="_blank">http://62.149.130.111/sessione.asp</font</a>>
  > >
  > > I have a recycle every 120 minutes, http connection timeout 900 seconds,
  > > session timeout 20 minutes.
  > >
  > > The problem is the same on several servers.
  > >
  > > Any idea?
  > >
  > > Stefano
  > >
  > >
  > >
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: IIS 6.0 asp Session problem 

What *type* of memory limit were you imposing -- virtual and/or private.
And how are you determining that the worker process never reached this
value -- which *type* of memory were you monitoring and with what tool. You
may be comparing apples and oranges, at which point the bug is "user-error"
and not in IIS6.

We've got demos and tests using both those values, so I'm pretty certain
they work...

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Stefano Cecconi" <webmaster.DeleteThis@technet.it> wrote in message
news:ea3$9ZGeDHA.2304@TK2MSFTNGP10.phx.gbl...
I found the cause :

disabling the recycle "after consuming too much memory" sessions work fine.

The strange thing is that my setting was to recycle at 500Mb, and the worker
process never reached this value, but it was recycling every 120 seconds...

A bug?

Stefano

"Robbie Wallis" <robbie.wallis.DeleteThis@virgin.net> ha scritto nel messaggio
news:%231TNlMDeDHA.2428@TK2MSFTNGP09.phx.gbl...
 > Its not always 120 sec with us its at random times but it always seems to
 > happen before the set idle time is reached
 >
 > We are seeing a ton of these warnings assuming 0x80 could be the idle
 > timeout?
 > A process serving application pool 'xxxxxxxxxx' terminated unexpectedly.
The
 > process id was '4944'. The process exit code was '0x80'. which sometimes
 > lead to this
 >
 > Application pool 'xxxxxxxxxxxxx' is being automatically disabled due to a
 > series of failures in the process(es) serving that application pool.
 >
 > Im assuming the latter is being caused by many of the previous errors
 >
 > Can we keep you informed of this to hopefully trace the problem?
 >
 > One other question. Im assuming with application pools if say you had 100
 > sites and 1 application pool that would use less memory than 100 sites
split
 > into 10 application pools?
 >
 > Thanks
 >
 > Robbie
 >
 > "David Wang [Msft]" <someone.DeleteThis@online.microsoft.com> wrote in message
 > news:OqhjNpBeDHA.2428@TK2MSFTNGP09.phx.gbl...
  > > Is it always 120 seconds?
  > >
  > > Unexpected loss of server variables usually means the worker process
 > exited
  > > for some reason (expected or unexpected), causing ASP to lose state (the
  > > other reason would be an ASP bug). A worker process exit/crash usually
 > have
  > > an event log message associated with it if it was not expected by IIS.
On
  > > the other hand, a configured worker process recycle would be an example
of
  > > an expected worker process exit when it triggers.
  > >
  > > I cannot reproduce the claimed session problem with my test Session ASP
  > > page. I have a page which uses the querystring to add a test session
  > > variable. I added a couple, then waited 3 minutes, and made another
 > request
  > > using the same session to add another session variable -- and I saw that
 > the
  > > previous variables still existed (so I definitely have an ASP page which
  > > kept session state > 120 seconds on IIS6).
  > >
  > > --
  > > //David
  > > IIS
  > > This posting is provided "AS IS" with no warranties, and confers no
 > rights.
  > > //
  > > "Stefano Cecconi" <webmaster.DeleteThis@technet.it> wrote in message
  > > news:eZe5vm8dDHA.828@TK2MSFTNGP11.phx.gbl...
  > > Hi,
  > >
  > > i have a problem with asp sessions : they expire after 120 seconds even
if
 > i
  > > have 20 minutes in my settings.
  > >
  > > I know i could use aspnet_state, but it doesn't solve the problem for
 > normal
  > > asp pages.
  > >
<font color=green>  > > <a style='text-decoration: underline;' href="http://62.149.130.111/sessione.asp</font" target="_blank">http://62.149.130.111/sessione.asp</font</a>>
  > >
  > > I have a recycle every 120 minutes, http connection timeout 900 seconds,
  > > session timeout 20 minutes.
  > >
  > > The problem is the same on several servers.
  > >
  > > Any idea?
  > >
  > > Stefano
  > >
  > >
  > >
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: IIS 6.0 asp Session problem 

Hi David,
We have the same problem. session timeout = 20mts in the
web.config, but it times out after 14 - 15 mts. idle
time. Sometimes I've seen time out around 10mts, if the
testing on this aspect, frequently. How do I disable
aspnet_wp recycle event. We are using IIS 5.1.

thanks
mahesh

 >-----Original Message-----
 >Ok. In that case, it really isn't an ASP session
problem but rather a known
 >generic problem between ASP state and Worker Process
recycling.
 >
 >Namely, ASP stores state in the process it runs in, and
if that process
 >recycles for whatever reason (i.e. worker process
crashed when running 3rd
 >party/custom code, worker process recycles normally due
to configuration,
 >etc), that state is lost.
 >
 >What you are seeing in the event log is evidence of the
former. Something
 >that was running in the application pool crashed,
bringing down the worker
 >process and hence any ASP state that was contained in
that process. A rapid
 >failure of worker process leads to the AppPool being
disabled and 503s
 >returned.
 >
 >So, your session problem is really an indication of
something else that's
 >going wrong on your system. With prior versions of IIS,
this probably would
 >have brought down your server -- with IIS6, it kept
going, but you noticed
 >the state loss. I would suggest you troubleshoot what
is crashing -- look
<font color=purple> >at IIS State: <a style='text-decoration: underline;' href="http://www.iisfaq.com/default.aspx?</font" target="_blank">http://www.iisfaq.com/default.aspx?</font</a>>
view=P197
 >
 >Thus, you can see that ASP.Net, with its session state
service, is immune to
 >this problem -- code can bring down ASP.Net
applications, but IIS6 will just
 >spin up another worker process, which retrieves its
state from the session
 >state service, and it's right back where it left off.
 >
 >Here is how to think about application
pools/isolation/memory consumption --
 >assume each website takes 1 MB of memory and each
application pool takes 1MB
 >of memory. 100 applications in one app pool takes 101
MB of memory.
 >However, if any of the 100 applications crash, it loses
state for the other
 >99. Meanwhile, if you have 10 applications in 10 app
pools, you use up 110
 >MB of memory, but if any of the applications crash, it
loses state for 9
 >others, not 99. So, you spend 9% more memory to bring
isolation to 9% of
 >applications. If you isolate each application in its
own app pool, you
 >spend 100% more memory to bring total isolation to 100%
apps.
 >
 >--
 >//David
 >IIS
 >This posting is provided "AS IS" with no warranties, and
confers no rights.
 >//
 >"Robbie Wallis" <robbie.wallis.TakeThisOut@virgin.net> wrote in
message
 >news:%231TNlMDeDHA.2428@TK2MSFTNGP09.phx.gbl...
 >Its not always 120 sec with us its at random times but
it always seems to
 >happen before the set idle time is reached
 >
 >We are seeing a ton of these warnings assuming 0x80
could be the idle
 >timeout?
 >A process serving application pool 'xxxxxxxxxx'
terminated unexpectedly. The
 >process id was '4944'. The process exit code was '0x80'.
which sometimes
 >lead to this
 >
 >Application pool 'xxxxxxxxxxxxx' is being automatically
disabled due to a
 >series of failures in the process(es) serving that
application pool.
 >
 >Im assuming the latter is being caused by many of the
previous errors
 >
 >Can we keep you informed of this to hopefully trace the
problem?
 >
 >One other question. Im assuming with application pools
if say you had 100
 >sites and 1 application pool that would use less memory
than 100 sites split
 >into 10 application pools?
 >
 >Thanks
 >
 >Robbie
 >
 >"David Wang [Msft]" <someone.TakeThisOut@online.microsoft.com> wrote
in message
 >news:OqhjNpBeDHA.2428@TK2MSFTNGP09.phx.gbl...
  >> Is it always 120 seconds?
  >>
  >> Unexpected loss of server variables usually means the
worker process
 >exited
  >> for some reason (expected or unexpected), causing ASP
to lose state (the
  >> other reason would be an ASP bug). A worker process
exit/crash usually
 >have
  >> an event log message associated with it if it was not
expected by IIS. On
  >> the other hand, a configured worker process recycle
would be an example of
  >> an expected worker process exit when it triggers.
  >>
  >> I cannot reproduce the claimed session problem with my
test Session ASP
  >> page. I have a page which uses the querystring to add
a test session
  >> variable. I added a couple, then waited 3 minutes,
and made another
 >request
  >> using the same session to add another session
variable -- and I saw that
 >the
  >> previous variables still existed (so I definitely have
an ASP page which
  >> kept session state > 120 seconds on IIS6).
  >>
  >> --
  >> //David
  >> IIS
  >> This posting is provided "AS IS" with no warranties,
and confers no
 >rights.
  >> //
  >> "Stefano Cecconi" <webmaster.TakeThisOut@technet.it> wrote in
message
  >> news:eZe5vm8dDHA.828@TK2MSFTNGP11.phx.gbl...
  >> Hi,
  >>
  >> i have a problem with asp sessions : they expire after
120 seconds even if
 >i
  >> have 20 minutes in my settings.
  >>
  >> I know i could use aspnet_state, but it doesn't solve
the problem for
 >normal
  >> asp pages.
  >>
<font color=green>  >> <a style='text-decoration: underline;' href="http://62.149.130.111/sessione.asp</font" target="_blank">http://62.149.130.111/sessione.asp</font</a>>
  >>
  >> I have a recycle every 120 minutes, http connection
timeout 900 seconds,
  >> session timeout 20 minutes.
  >>
  >> The problem is the same on several servers.
  >>
  >> Any idea?
  >>
  >> Stefano
  >>
  >>
  >>
 >
 >
 >
 >.
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: IIS 6.0 asp Session problem 

If you are using IIS5.1 (XP Pro), then we are not talking about the same
issue.

ASP.Net has its own configurable recycling. Check out its web.config for
more info.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Mahesh" <maheshtsm.TakeThisOut@netscape.net> wrote in message
news:007101c39731$ddcc47d0$a501280a@phx.gbl...
Hi David,
We have the same problem. session timeout = 20mts in the
web.config, but it times out after 14 - 15 mts. idle
time. Sometimes I've seen time out around 10mts, if the
testing on this aspect, frequently. How do I disable
aspnet_wp recycle event. We are using IIS 5.1.

thanks
mahesh

 >-----Original Message-----
 >Ok. In that case, it really isn't an ASP session
problem but rather a known
 >generic problem between ASP state and Worker Process
recycling.
 >
 >Namely, ASP stores state in the process it runs in, and
if that process
 >recycles for whatever reason (i.e. worker process
crashed when running 3rd
 >party/custom code, worker process recycles normally due
to configuration,
 >etc), that state is lost.
 >
 >What you are seeing in the event log is evidence of the
former. Something
 >that was running in the application pool crashed,
bringing down the worker
 >process and hence any ASP state that was contained in
that process. A rapid
 >failure of worker process leads to the AppPool being
disabled and 503s
 >returned.
 >
 >So, your session problem is really an indication of
something else that's
 >going wrong on your system. With prior versions of IIS,
this probably would
 >have brought down your server -- with IIS6, it kept
going, but you noticed
 >the state loss. I would suggest you troubleshoot what
is crashing -- look
<font color=purple> >at IIS State: <a style='text-decoration: underline;' href="http://www.iisfaq.com/default.aspx?</font" target="_blank">http://www.iisfaq.com/default.aspx?</font</a>>
view=P197
 >
 >Thus, you can see that ASP.Net, with its session state
service, is immune to
 >this problem -- code can bring down ASP.Net
applications, but IIS6 will just
 >spin up another worker process, which retrieves its
state from the session
 >state service, and it's right back where it left off.
 >
 >Here is how to think about application
pools/isolation/memory consumption --
 >assume each website takes 1 MB of memory and each
application pool takes 1MB
 >of memory. 100 applications in one app pool takes 101
MB of memory.
 >However, if any of the 100 applications crash, it loses
state for the other
 >99. Meanwhile, if you have 10 applications in 10 app
pools, you use up 110
 >MB of memory, but if any of the applications crash, it
loses state for 9
 >others, not 99. So, you spend 9% more memory to bring
isolation to 9% of
 >applications. If you isolate each application in its
own app pool, you
 >spend 100% more memory to bring total isolation to 100%
apps.
 >
 >--
 >//David
 >IIS
 >This posting is provided "AS IS" with no warranties, and
confers no rights.
 >//
 >"Robbie Wallis" <robbie.wallis.TakeThisOut@virgin.net> wrote in
message
 >news:%231TNlMDeDHA.2428@TK2MSFTNGP09.phx.gbl...
 >Its not always 120 sec with us its at random times but
it always seems to
 >happen before the set idle time is reached
 >
 >We are seeing a ton of these warnings assuming 0x80
could be the idle
 >timeout?
 >A process serving application pool 'xxxxxxxxxx'
terminated unexpectedly. The
 >process id was '4944'. The process exit code was '0x80'.
which sometimes
 >lead to this
 >
 >Application pool 'xxxxxxxxxxxxx' is being automatically
disabled due to a
 >series of failures in the process(es) serving that
application pool.
 >
 >Im assuming the latter is being caused by many of the
previous errors
 >
 >Can we keep you informed of this to hopefully trace the
problem?
 >
 >One other question. Im assuming with application pools
if say you had 100
 >sites and 1 application pool that would use less memory
than 100 sites split
 >into 10 application pools?
 >
 >Thanks
 >
 >Robbie
 >
 >"David Wang [Msft]" <someone.TakeThisOut@online.microsoft.com> wrote
in message
 >news:OqhjNpBeDHA.2428@TK2MSFTNGP09.phx.gbl...
  >> Is it always 120 seconds?
  >>
  >> Unexpected loss of server variables usually means the
worker process
 >exited
  >> for some reason (expected or unexpected), causing ASP
to lose state (the
  >> other reason would be an ASP bug). A worker process
exit/crash usually
 >have
  >> an event log message associated with it if it was not
expected by IIS. On
  >> the other hand, a configured worker process recycle
would be an example of
  >> an expected worker process exit when it triggers.
  >>
  >> I cannot reproduce the claimed session problem with my
test Session ASP
  >> page. I have a page which uses the querystring to add
a test session
  >> variable. I added a couple, then waited 3 minutes,
and made another
 >request
  >> using the same session to add another session
variable -- and I saw that
 >the
  >> previous variables still existed (so I definitely have
an ASP page which
  >> kept session state > 120 seconds on IIS6).
  >>
  >> --
  >> //David
  >> IIS
  >> This posting is provided "AS IS" with no warranties,
and confers no
 >rights.
  >> //
  >> "Stefano Cecconi" <webmaster.TakeThisOut@technet.it> wrote in
message
  >> news:eZe5vm8dDHA.828@TK2MSFTNGP11.phx.gbl...
  >> Hi,
  >>
  >> i have a problem with asp sessions : they expire after
120 seconds even if
 >i
  >> have 20 minutes in my settings.
  >>
  >> I know i could use aspnet_state, but it doesn't solve
the problem for
 >normal
  >> asp pages.
  >>
<font color=green>  >> <a style='text-decoration: underline;' href="http://62.149.130.111/sessione.asp</font" target="_blank">http://62.149.130.111/sessione.asp</font</a>>
  >>
  >> I have a recycle every 120 minutes, http connection
timeout 900 seconds,
  >> session timeout 20 minutes.
  >>
  >> The problem is the same on several servers.
  >>
  >> Any idea?
  >>
  >> Stefano
  >>
  >>
  >>
 >
 >
 >
 >.
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: IIS 6.0 asp Session problem