-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Tomcat-User,
We've been monitoring our old Tomcat4 servers with BigBrother. It just watches TCP port 8009 by sending a ping every 130 seconds. This has been working for us. If Tomcat starts taking a nose dive, it will close 8009 and BigBrother will pick it up and send an alert. Recently, however, we've introduced some Tomcat5 servers into our environment. We moved our BigBrother monitoring scripts to the new servers and they are showing up and down pretty much constantly. We're not seeing any performance issues, services are running just fine, webapps all appear to be working, and the logs don't show anything out of the ordinary. So my question is, is this normal behavior for Tomcat5? Is the regular closing of port 8009 normal? And is the type of monitoring I described the right type of monitoring for Tomcat5? If it's okay to monitor this way, is 130 seconds too low a threshold? Thanks for any clues. Regards, Dave - -- David Kaplowitz UNIT Unix Systems group Villanova University 610-519-6896 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCigO30nMoCk4O+jkRAuF4AJ9BZLrNaK9x2KGGw2Lmfhok/M6tfgCdEX99 yWjywD0eMjbsLc9arlG4uhA= =WkmL -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
