Thanks for the link. I didn't know about Nagios; it seems like a
pretty useful tool. I'll have to take for a spin.
About the Tomcat state issue, I actually got them resolved. I
basically followed Tim Funk's tips (see prior posts).
I modified some C code to get the UNIX PIDs straight from
Howdy,
Note that the premise of your question is flawed without a precise definition
of starting up and shutting down. Consider a tomcat instance with N
webapps, each of which with one ServletContextListener. Tomcat on startup will
send the contextInitialized event to each of these listeners.
: Re: Assessing Tomcat's State
Howdy,
Note that the premise of your question is flawed without a precise
definition
of starting up and shutting down. Consider a tomcat instance with N
webapps, each of which with one ServletContextListener. Tomcat on startup
will
send the contextInitialized event
On 8 Jun 2003 at 21:59, Euan Guttridge wrote:
slightly off subject : has anyone written a 'watchdog' for tomcat? Simply a
process that checks if tomcat is alive every x seconds, if dead restarts
tomcat.
I was after this a couple of months back. I found the solution in a list and
Howdy,
I use nagios for this: www.nagios.org.
Yoav Shapira
=
Yoav Shapira
[EMAIL PROTECTED]
__
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
Depending on your needs if you just need UP or down, you can use wget or a
similar agent.
You can also set CATALINA_PID in unix before calling the startup scripts and
the file referenced by CATALINA_PID will contain the process ID.
Or you can write a LifeCycle Listener to trap startup and
Thanks Tim,
Those suggestions work pretty well for checking the running and the
stopped states. The ones giving me a headache are really starting
up and shutting down.The only thing I can think of at this point
is to monitor the size of catalina.out and trigger an event went it
doesn't
The easy kluge is to hack the startup scripts (or write wrappers) around the
startup scripts to maintain this status in some file, for arguements sake:
cowbell.txt
In startup.sh -- echo starting cowbell.txt
In startup.sh, a timer does wgets on a static asset. Once the asset is
returned
That's a good idea. Thanks!
Take care,
-FB
On Saturday, June 7, 2003, at 03:23 PM, Tim Funk wrote:
The easy kluge is to hack the startup scripts (or write wrappers)
around the startup scripts to maintain this status in some file, for
arguements sake: cowbell.txt
In startup.sh -- echo
