You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2004/04/07 23:30:51 UTC
DO NOT REPLY [Bug 28270] New: -
java process watchdog
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=28270>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28270
java process watchdog
Summary: java process watchdog
Product: Commons
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: Enhancement
Priority: Other
Component: Daemon
AssignedTo: commons-dev@jakarta.apache.org
ReportedBy: alwold@asu.edu
When tomcat crashes with a segmentation fault, it doesn't have any automatic way
of starting back up. In a single server/single tomcat situation, this causes
users to get an internal server error if there's an apache front end, or just be
unable to connect if it's standalone, until the administrator notices and starts
it back up. Eliminating the segfault is the best solution, but sometimes not
possible (for example we have a DB2 driver that crashes the JVM about once every
48 hours). What I would like to have is watchdog functionality which starts
tomcat, then restarts it if it dies with a SIGSEGV (and probably logs the error
and/or notifies someone). I think jsvc would be able to deal with this pretty
easily.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org