Re: IIS6 doesn't show App Pools

From: Ken Schaefer (kenREMOVE_at_THISadopenstatic.com)
Date: 12/28/04


Date: Wed, 29 Dec 2004 00:12:18 +1100

Unless you've configure your web applications to recycle, then you should
see something in the Windows Event Log if the worker process servicing the
pool was shutdown unexpectedly. I think that takes care of (2)

(3) is not a problem *unless* the w3wp.exe process servicing the application
pool somehow terminates unexpectedly (meaning that everything stored
in-memory was lost). I suggest you look in your Windows Event Log for events
about this.

Otherwise, I suggest you start looking elsewhere. To maintain ASP session
state requires:
a) a ASPSession cookie value to be sent from the server to the client (check
this using a network sniffer like NetMon or Ethereal)
b) the browser to send the ASPSesion cookie back to the server on the next
request (again, check this using a network sniffer)
c) the server to recognise this as a valid, non-expired ASP Session ID

Cheers
Ken

"dw" <cougarmana_NOSPAM@uncw.edu> wrote in message
news:%23Dhlihs6EHA.1400@TK2MSFTNGP11.phx.gbl...
> Thanks, David. That's some useful info. As far as I know we're not running
> a Web Garden. How can we check if 2 or 3 apply to us? I think our ASP apps
> run in-process. How do we fix this problem? Thanks.
>
>
> "David Wang [Msft]" <someone@online.microsoft.com> wrote in message
> news:Obcipvj6EHA.1120@TK2MSFTNGP11.phx.gbl...
>> There are a couple of IIS6 Application Pool features that can cause your
>> situation:`
>> 1. You are using Web Garden with >1 processes.
>> 2. The worker process recycles in between requests
>> 3. You are storing application state in-process
>>
>> The core issue is where application state (like session state) is stored
>> and
>> accessible to the application's code. Default ASP behavior is to use
>> in-process state.
>>
>> When a process recycles, any in-process state is automatically lost.
>> When
>> you use a Web Garden and make requests to the server over >1 connections,
>> the requests will go to different worker processes -- which have no
>> access
>> to each other's in-process state.
>>
>> IIS5 (and IIS6 in IIS5 Compatibility Mode) does not have AppPool features
>> like Web Garden nor Recycling, so it would never see this sort of issue.
>>
>> --
>> //David
>> IIS
>> http://blogs.msdn.com/David.Wang
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> //
>> "dw" <cougarmana_NOSPAM@uncw.edu> wrote in message
>> news:esm$g3b6EHA.1300@TK2MSFTNGP14.phx.gbl...
>> Thanks, Ken. That's what we're thinking too -- IIS6 should run ASP apps
>> right out of the box. Our team searched quite a bit online until we found
>> info about this. I'll ask and see if we can find the references -- though
>> it
>> might be sometime in the new year before I'll have the info. The only way
>> we
>> found that our apps could work was to run in 5.0 Isolation Mode,
>> otherwise
>> session state was lost. For example, an app that required login and kept
>> that in a session variable would kick the user out if he/she clicked
>> submit
>> just 20 seconds later on the page. We tried setting the Session.timeout =
>> 40, but nothing made any difference. These apps had worked fine under
>> Windows 2000.
>>
>> Do you know what could cause ASP apps to not work correctly in IIS6?
>> Could
>> some other setting on the machine cause this issue? Any help would be
>> appreciated -- we really want to use the App Pools feature of IIS6. Happy
>> holidays :)
>>
>> "Ken Schaefer" <kenREMOVE@THISadopenstatic.com> wrote in message
>> news:eGImbvV6EHA.3820@TK2MSFTNGP11.phx.gbl...
>>> Hi,
>>>
>>> Were else have you seen this problem? There shouldn't be any problem
>>> with
>>> an IIS6 box being able to maintain ASP session variables.
>>>
>>> Cheers
>>> Ken
>>>
>>> "dw" <cougarmana_NOSPAM@uncw.edu> wrote in message
>>> news:Ob5jhYR6EHA.3708@TK2MSFTNGP14.phx.gbl...
>>>> Thanks, Jeremy, for your reply. We think we figured this out: We're
>>>> running II6 in 5.0 Isolation Mode because our session variables were
>>>> being lost in classic ASP applications. That's why we can't see the App
>>>> Pools folder -- that's specific to IIS6 mode.
>>>>
>>>> By the way, do you know why in IIS6 mode (with 5.0 Isolation mode
>>>> unchecked), we would not be able to keep our session variables? It was
>>>> only when we check the 5.0 Isolation Mode that ASP pages were able to
>>>> hold on to their session states. We'd like to run IIS in full 6.0 mode
>>>> were it not for this problem. We've read about it elsewhere, but no one
>>>> has any solution other than the 5.0 Isolation Mode. Thanks.
>>>>
>>>> "Jeremy Smith" <godtoall@hotmail.com> wrote in message
>>>> news:1103822315.087441.40540@c13g2000cwb.googlegroups.com...
>>>>> Are you able to see the Web Service Extensions?
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>
>



Relevant Pages

  • application pool not recycling
    ... process to recycle each 3 hours (Recycle worker processes ... But it seems that worker process did not recycle because ... So i checked the following 2 options in the pool properties ... Recycle worker process after consuming too much memory ...
    (microsoft.public.inetserver.iis)
  • Re: Delay in getting first page of web site
    ... IIS6 has a 15 minute idle activity timeout where it will unload ... and shut down the worker process handling a given application. ... To "fix" this means tuning your Application Pool properties such that they ...
    (microsoft.public.inetserver.iis)
  • Re: Sharepoint AppStart and End Events
    ... SPS really restricts some feature of ASP.net so that SPS ... can control the execution of extend site well. ... I'd suggest you can recycle the IIS ... the new architecture worker process contains all the dll ...
    (microsoft.public.sharepoint.portalserver.development)
  • Re: company web
    ... IIS shuts down the worker process ... > pool in IIS and disable recycling. ... > Application Pool and select Properties. ... >> the first time anyone opens the home page it takes 10 -15 seconds ...
    (microsoft.public.windows.server.sbs)
  • Re: application pool not recycling
    ... > process to recycle each 3 hours (Recycle worker processes ... > the worker process does not recycle at the specified time, ... > recycle, bla bla bla, the usual message. ... > Recycle worker process after consuming too much memory ...
    (microsoft.public.windows.server.general)