Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / August 2003

Tip: Looking for answers? Try searching our database.

Way to automatically recycle aspnet_wp work process when close to 100% CPU for certain period of time?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Luther Miller - 26 Aug 2003 18:18 GMT
I have a server setup that is dedicate to providing a "proxy" by exposing a
web service that calls methods in a 3rd party ActiveX control and then
returns the results. Sometimes, the aspnet_wp work process seems to get
"hung" - it goes to close to 100% CPU and stays that way. Under these
circumstance, it appears that it is really the ActiveX control causing the
problem. Running IISRESET from the command line resolves the issue, for a
while, at least.

1) Is there a way to configure ASP.NET so that if the worker process is
detected at very high CPU (>80%) for longer than a certain period of time,
it will automatically recycle it?
2) I think it might be a threading issue. Is there an attribute I can set in
a Web Service, or in a configuration file, so that it will work better with
Active X controls?
John Viele - 26 Aug 2003 21:46 GMT
My $0.02 is below...

"Luther Miller" <luther@nowhere.invalid> wrote
-snip-

> 1) Is there a way to configure ASP.NET so that if the worker process is
> detected at very high CPU (>80%) for longer than a certain period of time,
> it will automatically recycle it?

Not a built-in way (at least that I've ever heard of), but you could
consider writing a windows service that kills it periodically.  Probably not
the ideal approach.

> 2) I think it might be a threading issue. Is there an attribute I can set in
> a Web Service, or in a configuration file, so that it will work better with
> Active X controls?

If the problem is the ActiveX control itself, I'd advise just find another
component that does the job for you and stop using the one causing the
problem.  I'm sure you thought of that, so if instead the problem IS being
cause by calling the control on multiple threads and possibly causing
concurrency errors, then simply wrap your calls to that component in a
function that uses a Mutex to prevent multiple threads from trying to use it
simultaneously.  Mutex is, of course, explained in the MSDN help.

-jv
Luther Miller - 27 Aug 2003 16:50 GMT
Unfortunately I am stuck with the ActiveX control - it is for access to a
3rd party data provider, and there are no other options in this case.
Interestingly, I believe that the problem may be an STA vs. MTA issue.

I am suspicious that the control is designed for STA use. Web Services will
call COM components using MTA by default. There does not appear to be an
easy way to change this behavior (see
http://support.microsoft.com/default.aspx?scid=kb;en-us;303375).

However, it looks like I will have to find one...

> My $0.02 is below...
>
[quoted text clipped - 24 lines]
>
> -jv

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.