Knowing if application is "alive"

[arfinmail]

I have 4 applications which are supposed to run 24/7. How can I make a
monitor application to know if they're running fine?

The best I can come up with is making them update a file/DB every X
amount of time and have the monitor app check that mark. If the mark
haven't updated then it means the program stopped. The programs do
their thing multithreaded so we don't have the problem of waiting for
the main thread to finish.

But this is so rustic that I think there's got to be a better way.
I'm hoping of something like sending an event over the network from the
running app to the monitor. This way the monitor will just sit there
listening to the other apps and if it stops receiving a message the
notify it.

[Shane Story]

why not have a LISTENER/Client (TCPIP)?

Monitor would be the listener and apps would be clients. They'd just need
the monitor's IP.

Is this possible?

Thanks,

Shane

ps. just an Idea
<ar*******@yahoo.com> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com...

I have 4 applications which are supposed to run 24/7. How can I make a
monitor application to know if they're running fine?

The best I can come up with is making them update a file/DB every X
amount of time and have the monitor app check that mark. If the mark
haven't updated then it means the program stopped. The programs do
their thing multithreaded so we don't have the problem of waiting for
the main thread to finish.

But this is so rustic that I think there's got to be a better way.
I'm hoping of something like sending an event over the network from the
running app to the monitor. This way the monitor will just sit there
listening to the other apps and if it stops receiving a message the
notify it.

[DevNick]

Have the running apps log an event, then remotely read the event logs and
scan for the messages. If you dont see them its not running(or at least
properly). If they have write they can even log the messages to the machine
your monitoring and to a specific log(instead of the standard logs). this
way you dont have to read through huge files.

You can also use SMNP traps as well.

"Shane Story" <sh**************@dv-corp.com> wrote in message
news:OW**************@TK2MSFTNGP14.phx.gbl...

why not have a LISTENER/Client (TCPIP)?

Monitor would be the listener and apps would be clients. They'd just need
the monitor's IP.

Is this possible?

Thanks,

Shane

ps. just an Idea
<ar*******@yahoo.com> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com...

I have 4 applications which are supposed to run 24/7. How can I make a
monitor application to know if they're running fine?

The best I can come up with is making them update a file/DB every X
amount of time and have the monitor app check that mark. If the mark
haven't updated then it means the program stopped. The programs do
their thing multithreaded so we don't have the problem of waiting for
the main thread to finish.

But this is so rustic that I think there's got to be a better way.
I'm hoping of something like sending an event over the network from the
running app to the monitor. This way the monitor will just sit there
listening to the other apps and if it stops receiving a message the
notify it.