aspnet_wp.exe process hangs

[bostro]

First, I am not the developer of this application, merely the system
administrator. The developer is a contractor and somewhat unavailable
at this time.

Environment Microsoft Windows 2000 Server, IIS 5.0, .NET Framework 1.1
(with the hotfix applied).

At random times, the aspnet_wp.exe stops responding and customers are
unable to load any of the pages for this particular application. The
pages just clock on customers machines. The thread count for the
aspnet_wp.exe process grows and doesn't reduce. Sometimes this thread
count will go up significantly 5 to 7 hours before the application
hangs and stay up, but not max out. The application is not recognized
as deadlocked or idle. Killing the aspnet_wp.exe process under task
manager releases the threads and then people are able to load pages.

We are not able to recreate the hang at will or identify what
circumstances cause the hang

Anyone have any ideas or suggestions? This is a very random
occurrance often happening during times when there is light or no
usage of the application.

Denise

 

[Alvin Bruney [MVP]]

It seems to be an issue with code. You will need a programmer to go in and
take a look at the code. There's not a whole lot you can do from a system
administrator stand point.

 

[hb]

First, I am not the developer of this application, merely the system
administrator. The developer is a contractor and somewhat unavailable
at this time.

Environment Microsoft Windows 2000 Server, IIS 5.0, .NET Framework 1.1
(with the hotfix applied).

At random times, the aspnet_wp.exe stops responding and customers are
unable to load any of the pages for this particular application. The
pages just clock on customers machines. The thread count for the
aspnet_wp.exe process grows and doesn't reduce. Sometimes this thread
count will go up significantly 5 to 7 hours before the application
hangs and stay up, but not max out. The application is not recognized
as deadlocked or idle. Killing the aspnet_wp.exe process under task
manager releases the threads and then people are able to load pages.

We are not able to recreate the hang at will or identify what
circumstances cause the hang

Anyone have any ideas or suggestions? This is a very random
occurrance often happening during times when there is light or no
usage of the application.

Denise

There are several factors at work here, Denise. We are currently going
through a painful process of diagnosing and finding a solution to the same
problem. It's been extremely frustrating.

If I remember I will try to come back and post if we find any real
solutions.

-Hillarie

 

[hb]

First, I am not the developer of this application, merely the system
administrator. The developer is a contractor and somewhat unavailable
at this time.

Environment Microsoft Windows 2000 Server, IIS 5.0, .NET Framework 1.1
(with the hotfix applied).

At random times, the aspnet_wp.exe stops responding and customers are
unable to load any of the pages for this particular application. The
pages just clock on customers machines. The thread count for the
aspnet_wp.exe process grows and doesn't reduce. Sometimes this thread
count will go up significantly 5 to 7 hours before the application
hangs and stay up, but not max out. The application is not recognized
as deadlocked or idle. Killing the aspnet_wp.exe process under task
manager releases the threads and then people are able to load pages.

We are not able to recreate the hang at will or identify what
circumstances cause the hang

Anyone have any ideas or suggestions? This is a very random
occurrance often happening during times when there is light or no
usage of the application.

Does the application support file uploads? I think our problem is related
to file uploads.

 

[bostro]

Does the application support file uploads? I think our problem is related
to file uploads.

No, the application does not support file uploads. It does have a link
to a database and loads the information from the database into a form
for a pick list. That part seems to be working pretty well.

Denise

 

[nvraman19]

As in one of the replies mentioned, it has nothing to do with system
administration. It is more related to programming. If the
application is interacting with COM component (through interop) this
may occur. When .net component communicates with COM this scenario
occurs. If this occurs then the memory taken by the process
(aspnet_wp.exe) will increase as observed by you, and even without
you restarting the process, the process will be resetted. Typically
when memory utilisation of aspnet_wp.exe reaches some % of RAM (which
can be customised), the application will be restarted automatically,
so that all your viewstates, sessions will be lost.
As far as my knowledge goes, Concentrate on the method which calls
that com object and correct it appropriately.
Regards,
N.Venkat

 

[hb]

As in one of the replies mentioned, it has nothing to do with system
administration. It is more related to programming. If the
application is interacting with COM component (through interop) this
may occur. When .net component communicates with COM this scenario
occurs. If this occurs then the memory taken by the process
(aspnet_wp.exe) will increase as observed by you, and even without
you restarting the process, the process will be resetted. Typically
when memory utilisation of aspnet_wp.exe reaches some % of RAM (which
can be customised), the application will be restarted automatically,
so that all your viewstates, sessions will be lost.
As far as my knowledge goes, Concentrate on the method which calls
that com object and correct it appropriately.

Yet another possible, cause, yes. My app has several COM objects that are
accessed through Interop.

Bostro - You can check this by looking in the /bin directory of the web
folder. If any of the files contain the text "interop" then you know the
app uses COM objects.

Still working on this issue.........

 

[Guest]

aspnet_wp.exe (V 1.1 (4322)) hangs on Win XP only during multiple access to Web Service. This occurs when accessin
an .asmx file but does not happen when accessing a similar aspx page. It does not occur on Win 2000 server with the same .Net framework V 1.1 (4322). The Web service makes api calls to win 32 thread safe dlls