The simplest thing which comes into my mind is (if the monitor is your own
work)
monitor an additional file, the "heartbeat file".
- When the monitor application starts it generates the file and monitors its
existence
- When it ends, it deletes the file
- If the monitor app recognizes that the file is deleted (by external
programs)
  it stops


Jan


> -----Ursprüngliche Nachricht-----
> Von: Dick, Brian E. [mailto:[EMAIL PROTECTED]
> Gesendet am: Mittwoch, 19. Januar 2005 14:18
> An: Ant Users List
> Betreff: Stopping an ant target
> 
> This is more of a java question, but I would appreciate your help.
> 
> I have a java application that I start from ant. This program
> continuously monitors our database for cpu utilization, connection
> attempts, and other general health statistics.
> 
> Currently, when I want to stop the application for maintenance, I kill
> its process. Yuk! What is a more graceful way of stopping my java
> application? Should I make it a RMI server and use a RMI 
> client to stop
> it? I have never done RMI, but I'm sure I can find examples. 
> Is there a
> simpler way to accomplish this?
> 
> Thanks,
> BEDick
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

Reply via email to