John Viele
8/26/2003 8:47:00 PM
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