this article is taken from a blog : http://prefetch.net/blog/index.php/2008/01/29/getting-alerts-when-java-processes-crash/
Getting alerts when Java processes crash
When bugs occur in the Java runtime environment, most administrators want to get notified so they can take corrective action. These actions can range from restarting a Java process, collecting postmortem data or calling in application support personnel to debug the situation further. The Java runtime has a number of useful options that can be used for this purpose. The first option is "-XX:OnOutOfMemoryError", which allows a command to be run when the runtime environment incurs an out of memory condition. When this option is combined with the logger command line utility:
$ java -XX:OnOutOfMemoryError="logger Java process %p encountered an OOM condition" …
Syslog entries similar to the following will be generated each time an OOM event occurs:
Jan 21 19:59:17 nevadadev root: [ID 702911 daemon.notice] Java process 19001 encountered an OOM condition
Another super useful option is "-XX:OnError", which allows a command to be run when the runtime environment incurs a fatal error (i.e., a hard crash). When this option is combined with the logger utility:
$ java -XX:OnError="logger -p Java process %p encountered a fatal condition" …
Syslog entries similar to the following will be generated when a fatal event occurs:
Jan 21 19:52:17 nevadadev root: [ID 702911 daemon.notice] Java process 19004 encountered a fatal condition
The options above allow you to run one or more commands when these errors are encountered, so you could chain together a postmortem debugging tool, a utility (logger or mail) to generate alerts, and a restarter script to start a new Java process (this assumes you aren't using SMF). Nice!
Thanks "matty"
enjoy..
--
Ravi Kr. Gupta
http://techdc.blogspot.com
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.