Windows Task Scheduler

[twt4757]

I have an application on a web server that occasionally hangs when a user tries to access and will eventually time out. A restart will fix the issue, but I wanted to put some sort of task in place that would automatically restart if it detected a lag/hang/timeout in the application as opposed to someone going into the web server and doing it manually.

Does anyone know how I could set this up using the windows task scheduler? I see a way to preform an action when a specific event is logged, but I'm not sure how to configure it to pick up on a specific application timing out/hanging.

Any help would be greatly appreciated.

Thanks.

 

[Kaktussoft]

What webserver software? Is it a php application, or sort of plugin so a DLL? Please explain.

Waht fixes it, simply restarting webserver or the application?

 

[twt4757]

It is a web application and it will require a restart of the service, which I already have a custom .bat file to handle.

 

[Kaktussoft]

It is a web application and it will require a restart of the service, which I already have a custom .bat file to handle.

So not a webserver at all?

It's a service listening on a tcp/ip port ... just like a mailserver or database server?

 

[twt4757]

Its a web application running on a web server.

 

[Kaktussoft]

Its a web application running on a web server.

web server is a piece of software like apache or IIS ?
Or do you mean by saying web server: The hardware where I host web applications

 

[twt4757]

it is a web application running on IIS on a web server.

 

[Kaktussoft]

it is a web application running on IIS on a web server.

Whole IIS is hanging than, or only the application (is it a DLL?)?

 

[Kaktussoft]

Are you simply killing the web application process and restarting it to make it work again (for some time)?

Is it in a loop, or just freezing?

 

[twt4757]

Right, just killing the process then restarting. It's not the whole server or IIS that's freezing, just one application.

 

[Kaktussoft]

Right, just killing the process then restarting. It's not the whole server or IIS that's freezing, just one application.

Very difficult to detect a freeze or loop. I think it is in a loop (using a lot of cpu time and actually doing nothing). Or it's waiting for an event that doesn't happen. Maybe you can add debugging or let it log things in some file. Otherwise i don't know how to solve freeze and loop problems.

Does application processes some requests that end let's say in 1 sec (normally)? If so, let a job run continuously and do a dummy transaction every minute. If it doesn't end the transaction in 5 seconds, you assume it a freeze. Kill and restart web application then.