K
Ken Barrett
I apologize in advance for cross-posting, but I have noted that others
have experienced similar issues and was hoping that someone could
help.
Briefly, I am working on an ASP.NET content management application
written in C#. running on .NET Framework 1.1/W2K/IIS5. The
application uses the Microsoft WebService Behavior to generate a tree
of "folders" in a frame on the left hand side. The user can click on
a "folder", and the contents are rendered in the top frame on the
right. The user can then click on individual items (e.g. documents)
and they are displayed in the bottom frame on the right. The objects
themselves are stored in a strongly typed session object, and I am
starting to suspect that might be the issue.
Under minimal load (i.e. 1 user), the application runs for a short
while, and then the aspnet_wp.exe process hangs. It is never at the
same point (i.e. different users experience the hang at different
points), but the one thing that is fairly common is that task manager
shows that the CPU is happy (i.e. running around 3%-12%), and the
aspnet_wp.exe process has consumed approximately 65MB of memory. The
user can click on links in the browser (IE 6.0 SP1), and our
javascript runs, but no requests are logged on the server (I have used
Perfmon to verify that no requests are queued).
The IIS log shows a lot of 304 status codes for images, with a few 500
10054 status codes mixed in. In addition, there are sporadic
instances of a status code of 500 with no other information (i.e. just
the time and the value 500). However, at the point that the
application hangs, the log shows a status of 200 for the last request
handled.
I have used IISState, AD+ and WinDbg to try an pinpoint what is going
on. I have followed the articles at Microsoft on using WinDbg and SOS
to pinpoint the cause of the hang. The !threads command shows that we
have 1 dead thread, and further analysis shows that all of the threads
have a Suspend value of 1. Which, according to the articles, means
they will not run. However, I cannot for the life of me figure out
why or how. I could use some help deciphering the dumps and logs,
since I am new to WinDbg. I didn't include the log here, but I can in
future posts.
Any help that any can offer is greatly appreciated.
Thanks in advance,
Ken Barrett
MCP .NET
have experienced similar issues and was hoping that someone could
help.
Briefly, I am working on an ASP.NET content management application
written in C#. running on .NET Framework 1.1/W2K/IIS5. The
application uses the Microsoft WebService Behavior to generate a tree
of "folders" in a frame on the left hand side. The user can click on
a "folder", and the contents are rendered in the top frame on the
right. The user can then click on individual items (e.g. documents)
and they are displayed in the bottom frame on the right. The objects
themselves are stored in a strongly typed session object, and I am
starting to suspect that might be the issue.
Under minimal load (i.e. 1 user), the application runs for a short
while, and then the aspnet_wp.exe process hangs. It is never at the
same point (i.e. different users experience the hang at different
points), but the one thing that is fairly common is that task manager
shows that the CPU is happy (i.e. running around 3%-12%), and the
aspnet_wp.exe process has consumed approximately 65MB of memory. The
user can click on links in the browser (IE 6.0 SP1), and our
javascript runs, but no requests are logged on the server (I have used
Perfmon to verify that no requests are queued).
The IIS log shows a lot of 304 status codes for images, with a few 500
10054 status codes mixed in. In addition, there are sporadic
instances of a status code of 500 with no other information (i.e. just
the time and the value 500). However, at the point that the
application hangs, the log shows a status of 200 for the last request
handled.
I have used IISState, AD+ and WinDbg to try an pinpoint what is going
on. I have followed the articles at Microsoft on using WinDbg and SOS
to pinpoint the cause of the hang. The !threads command shows that we
have 1 dead thread, and further analysis shows that all of the threads
have a Suspend value of 1. Which, according to the articles, means
they will not run. However, I cannot for the life of me figure out
why or how. I could use some help deciphering the dumps and logs,
since I am new to WinDbg. I didn't include the log here, but I can in
future posts.
Any help that any can offer is greatly appreciated.
Thanks in advance,
Ken Barrett
MCP .NET
