Re: Knowing if application is "alive"
- From: "Shane Story" <shanesREMOVETHIS@xxxxxxxxxxx>
- Date: Mon, 25 Apr 2005 11:37:15 -0500
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
<arfinmail@xxxxxxxxx> wrote in message
news:1114183570.821163.227330@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>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.
>
.
- Follow-Ups:
- Re: Knowing if application is "alive"
- From: DevNick
- Re: Knowing if application is "alive"
- References:
- Knowing if application is "alive"
- From: arfinmail
- Knowing if application is "alive"
- Prev by Date: Re: how know?
- Next by Date: Re: Not just computer language
- Previous by thread: Knowing if application is "alive"
- Next by thread: Re: Knowing if application is "alive"
- Index(es):
Relevant Pages
|