I would consider two monitors: - One local that restarts tomcat if the process is not alife anymore. For this monitor ps can be enough. More sophisticated checks should only be done if you are shure that you want to automatically restart tomcat if this checks fail.
- One remote that calls/mails the service if tomcat is not working. What exactly 'not working' means and which checks you have to implement to verify that depends on the application and the requirements. > -----Original Message----- > From: Turner, John [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 25, 2003 9:42 PM > To: 'Tomcat Users List' > Subject: RE: crontab problems > > Well, to be paranoid, it would have to be on a remote machine. If it > wasn't, a network outage would take your app down, but your > monitor would keep right on merrily testing your web app. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
