Skip to main content

Managing tomcat application

Tomcat is a servlet application which is ready to use after download. There is no need of installing this application. We can directly start or stop it from the bin directory. 

So in such case we should go to the bin directory in the CATALINA_HOME or else we need to use the startup script along with its absolute path. And the same is needed to shut it down.

We can use the below script to manage the tomcat application and we neither need to go to the CATALINA_HOME nor to use the absolute path. All we need to do is to change the permissions to make it executable and copy that to /sbin and /etc/init.d/ directories. If we copy this into /etc/init.d/ then also we need to mention the absolute path but we can easily memorize it as we know all the startup scripts exists there. But if we copy that into /sbin then there is absolutely no need of mentioning the path of the file.

We can use this like below:
 # tomcat start|stop|restart|status  
#!/bin/bash  
# Author : Arjun Shrinivas  
# Purpose : This script is usefull for managing tomcat  
   
 CATALINA_HOME=/u01/tomcat  
 OPTION=$1  
   
 echo "Usage: `basename $0` start|stop|restart|status"  
   
 case $OPTION in  
 start)  
      echo "Starting tomcat"  
      $CATALINA_HOME/bin/startup.sh  
 ;;  
 stop)  
      echo "Stopping tomcat"  
      $CATALINA_HOME/bin/shutdown.sh  
 ;;  
 restart)  
      PID=`ps -ef | grep catalina | grep -v grep | awk '{print $2}'`  
      if [ -z $PID ]  
      then  
           echo "Starting tomcat"  
           $CATALINA_HOME/bin/startup.sh  
      else  
           echo "Stopping tomcat"  
           $CATALINA_HOME/bin/shutdown.sh  
           sleep 20  
           PID=`ps -ef | grep catalina | grep -v grep | awk '{print $2}'`  
           if [ -z $PID ]  
           then  
                echo "Starting tomcat"  
                $CATALINA_HOME/bin/startup.sh  
           else  
                echo -e "Unable to shutdown tomcat. Force killing tomcat PID : $PID"  
                kill -9 $PID  
                echo "Starting tomcat"  
                $CATALINA_HOME/bin/startup.sh  
           fi  
      fi  
 ;;  
 status)  
      PID=`ps -ef | grep catalina | grep -v grep | awk '{print $2}'`  
      if [ ! -z $PID ]  
      then  
           echo -e "Tomcat is running on pid : $PID"  
      else  
           echo -e "Tomcat is not running"  
      fi  
 ;;  
 *)  
      echo "Invalid operation"  
 ;;  
 esac  
   
 # END

Comments

Popular posts from this blog

Ansible Installation Steps Red Hat Enterprise Linux 7

Ansible is a simple IT automation engine that automates provisioning, configuration management, application deployment and many other IT needs.  Designed for multi-tier deployments, ansible models your IT infrastructure by describing how all of your systems interrelate, rather than just managing one system at a time. In this Article we are going to learn Ansible Installation Steps Red Hat Enterprise Linux 7 – RHEL 7. It uses no agents and no additional custom security infrastructure, so it’s easy to deploy – and most importantly, it uses a very simple language YAML that allow you to describe your automation jobs in a way that approaches plain English. Ansible Architecture Ansible works by connecting to your nodes and pushing out small programs, called “Ansible modules” to them. These programs are written to be resource models of the desired state of the system. Ansible then executes these modules using SSH Protocol, and removes them when finished. Your library of modul...

Troubleshooting Tomcat using Catalina log

Troubleshooting Tomcat using Catalina log We can get the  catalina  logs in  $CATALINA_HOME/logs Here we'll have a  catalina.out We can see some huge info in that log file. If we want to what exactly happens since the start of tomcat then we need to log that into a new file. By default we have log rotation enabled on this logs. For now let us stop tomcat and nullify the catalina.out file and then start tomcat to have some new info in the catalina.out # service tomcat stop # cd $CATALINA_HOME/logs # :> catalina.out (or) cat /dev/null > catalina.out # ll catalina.out -rw-r----- 1 root root 0 Feb 18 16:19 catalina.out # service tomcat start # ll catalina.out -rw-r----- 1 root root 17341 Feb 18 16:21 catalina.out We can see the log being written after the start of tomcat. Now we can notice the instance giving some information about the starting of tomcat, about the configuration for the startup, path of the servlet instance for which the log is re...

Customizing Java Virtual Machine

Customizing Java Virtual Machine Customizing the  catalina.sh CATALINA_OPTS CATALINA_OPTS="$CATALINA_OPTS $JPDA_OPTS" By default the CATALINA_OPTS line will looks like above. Among which the JPDA_OPTS is used to provide the debug options for the catalina script. Now we need to edit this line and can add our custom options like the size of initial memory of JVM (min. size), the size of memory of the JVM (max. size) it can grow upto, garbage collection options, etc. Add the below at the end of the  CATALINA_OPTS  line -Xms128m -Xmx256m -Xms  means Extended Minimum Size which is the min / initial size of a JVM to start with -Xmx  means Extended Maximum Size which is the max size upto which a JVM can grow