Rich
Wed May 03 10:23:06 CDT 2006
When a user logs in, depending on his role, he see different menus.
Normally he would select a menu and see content that is pulled from certain
html pages and put into a container.aspx page that is served to the users
browser.
When the problem occurs the container.aspx page does not have any content.
To the app developers it looks like this is because the app does not have
permissions to access the html content to create the container.aspx page.
But it is not a permissions issue. This problem usually take a few days to
start randomly appearing on various web servers in the farm. If we let the
problem go all the servers in the farm will exhibit the problem. We
temporarily fix the problem with a stop\restart of the app pool. I know a
recycle usually automatically occurs every 29 hours but that is not taking
care of the problem.
From your response it would leave me to believe that our problem comes from
holding client connections or maybe session state information too long? What
resource could depleted or is something getting hung up? We have 6 servers
and very minimal traffic to be already experiencing resource issues. About
20-30 peak connections per server.
"David Wang [Msft]" <someone@online.microsoft.com> wrote in message
news:ey0J9TlbGHA.4672@TK2MSFTNGP04.phx.gbl...
> What do you mean by "stops creating certain dynamic pages" - how does your
> application work?
>
> Recycling should work. It definitely has to differ from Stop/Start because
> it still keeps *some* state inside of IIS, for example, so that
> connections are not dropped across an application pool recycle (whereas
> app pool stop/start definitely allows the client to see a 503 while the
> app pool is stopped and your client-side connections all disconnect on a
> stop/start).
>
> So, what you are saying is that your app is interacting with IIS6 in such
> a way that the problem is not with state maintained inside of w3wp.exe,
> such as threads/memory, because that stuff goes away on a recycle and so
> should fix itself on a recycle, but rather depends on the state that IIS
> preserves for a recycle but purges for a stop/start.
>
> Thus, I want to know what exactly your application is doing and what
> "creating dynamic pages" means, because creation of dynamic pages should
> not be tied to any IIS state.
>
> --
> //David
> IIS
>
http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> //
>
> "Rich" <Rich@community.nospan> wrote in message
> news:e5e9w3gbGHA.4604@TK2MSFTNGP02.phx.gbl...
>> We have an web application that stops creating certain dynamic pages
>> after running for a week or so. The app pool recycle does not take care
>> of the problem but a stop and restart of the pool does take care of the
>> problem. So what is carried over in a recycle that does not carry over on
>> a stop\start? What does a stop\start of the app pool tell me that could
>> lead me to what is causing the problem? memory? threads? Any help is
>> appreciated thanks.
>>
>
>