Vineet Manohar is CTO / Co-Founder of online Car Search Engine, iSeeCars.com. Vineet is a DZone MVB and is not an employee of DZone and has posted 20 posts at DZone. You can read more from them at their website. View Full User Profile

How to Automatically Recover Tomcat From Crashes

06.28.2010
| 9752 views |
  • submit to reddit

Tomcat occasionally crashes if you do frequent hot-deploys or if you are running it on a machine with low memory. Every time tomcat crashes someone has to manually restart it, so I wrote a script which automatically detects that tomcat has crashed and restarts it.

Here’s the pseudo logic:

every few minutes {
check tomcat status;

if (status is "not running") {
start tomcat;
}
}
every few minutes {
  check tomcat status;

  if (status is "not running") {
    start tomcat;
  }
}

Here’s a shell script to implement the above logic. It assumes that you are running on a unix/linux system and have /etc/init.d/tomcat* script setup to manage tomcat.

Adjust the path to “/etc/init.d/tomcat” in the script below to reflect the correct path on your computer. Sometimes it is called /etc/init.d/tomcat5 or /etc/init.d/tomcat6 depending on your tomcat version. Also make sure that the message “Tomcat Servlet Container is not running.” matches with the message that you get when you run the script when tomcat is stopped.

#! /bin/sh
SERVICE=/etc/init.d/tomcat
STOPPED_MESSAGE="Tomcat Servlet Container is not running."

if [ "`$SERVICE status`" == "$STOPPED_MESSAGE"];
then
{
$SERVICE start
}
fi
#! /bin/sh
SERVICE=/etc/init.d/tomcat
STOPPED_MESSAGE="Tomcat Servlet Container is not running."

if [ "`$SERVICE status`" == "$STOPPED_MESSAGE"];
then
{
  $SERVICE start
}
fi

To run the script every 10 minutes:

1. Save the above script to “/root/bin/recover-tomcat.sh”.

2. Add execute permission:

chmod +x /root/bin/recover-tomcat.sh  
chmod +x /root/bin/recover-tomcat.sh

3. Add this to root’s crontab, type the following as root:

crontab -e  
crontab -e

4. Add the following lines to the crontab:

# monitor tomcat every 10 minutes  
*/10 * * * * /root/bin/recover-tomcat.sh  
# monitor tomcat every 10 minutes
*/10 * * * * /root/bin/recover-tomcat.sh

What if I don’t have /etc/init.d/tomcat* script on my computer?

Tomcat creates a pid file, typically in the TOMCAT_HOME/bin directory. This file contains the process id of the tomcat process running on the machine. The pseudo logic in that case would be:

 if (the PID file does not exist) {  
// conclude that tomcat is not running
start tomcat
}
else {
read the process id from the PID file
if (no process that id is running) {
// conclude that tomcat has crashed
start tomcat
}
}
if (the PID file does not exist) {
  // conclude that tomcat is not running
  start tomcat
}
else {
  read the process id from the PID file
  if (no process that id is running) {
    // conclude that tomcat has crashed
    start tomcat
  }
}

You can implement the above logic as follows. The following is experimental and is merely a suggested way, test it on your computer before using it.

# adjust this to reflect tomcat home on your computer
TOMCAT_HOME=/opt/tomcat5

if [ -f $TOMCAT_HOME/bin/tomcat.pid ]
then
echo "PID file exists"
pid="`cat $TOMCAT_HOME/bin/tomcat.pid`"
if [ "X`ps -p $pid | awk '{print $1}' | tail -1`" = "X"]
then
echo "Tomcat is running"
else
echo "Tomcat had crashed"
$TOMCAT_HOME/bin/startup.sh
fi
else
echo "PID file does not exist. Restarting..."
$TOMCAT_HOME/bin/startup.sh
fi
# adjust this to reflect tomcat home on your computer
TOMCAT_HOME=/opt/tomcat5

if [ -f $TOMCAT_HOME/bin/tomcat.pid ]
then
  echo "PID file exists"
  pid="`cat $TOMCAT_HOME/bin/tomcat.pid`"
  if [ "X`ps -p $pid | awk '{print $1}' | tail -1`" = "X"]
  then
    echo "Tomcat is running"
  else
    echo "Tomcat had crashed"
    $TOMCAT_HOME/bin/startup.sh
  fi
else
  echo "PID file does not exist. Restarting..."
  $TOMCAT_HOME/bin/startup.sh
fi

Why would tomcat crash?

The most common reason is low memory. For example, if you have allocated 1024MB of max memory to tomcat and enough memory is not available on that machine. Other reasons may involve repeated hot-deploys causing memory leaks, rare JVM bugs causing the JVM to crash.

 

From http://www.vineetmanohar.com/2010/06/howto-auto-recover-tomcat-crashes

Published at DZone with permission of Vineet Manohar, author and DZone MVB.

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)

Comments

Michael Eric replied on Wed, 2012/09/26 - 3:36pm

I understand the logic of wanting to use a script like this, but I do wonder if in doing so, you end up treating the symptoms rather than addressing the cause of the problem?

From a business point of view, if the technology I am using in production keeps crashing I would want to know how often this occurs, what I am doing to cause the crashes and whether these two in combination warrant me investigating the use of alternate technologies? Is this script something that you have/would use in production, or is it something you think that is useful for individual developers?

What are your thoughts about how this could be integrated into a wider monitoring solution so that technical issues are not masked from the business?

linux archive 

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.