====== Restarting An Application Container ======

Author: Sophie Renshaw

===== Introduction =====

In various cases, such as in the event of an outage, or during an upgrade, it is necessary to restart (bounce) an application container. This page describes the process of restarting an application container successfully. 

It is important to note that if you are restarting a container in the event of an outage that you run the outage scripts as per the following page: [[support:outage_process_backups|Outage Process Backups]]

----

===== Steps to restart container =====

For each app handler make sure that you have the application and catalina logs open while performing the restart
      The catalina logs can be found in /var/tomcat/<Application>/logs
      The application logs can be found in /logs/grails or /usr/local/logs (Errigal QA)
The shutdown and startup scripts are located in the /var/tomcat/<Application>/bin folder
Shutdown (use sudo for SNMP Manager):
      cd /var/tomcat/Ticketer/bin
      ./shutdown.sh
Check that application has stopped using logs and process list
      ps -edf | grep java
      ps -edf | grep -i Ticketer (-i for case insensitive)
Once process list shows no process listed for the application, application had been shutdown
If process list is still showing application after shutdown it may be necessary to kill the process:
      sudo kill -9 <PROCESS ID>
Startup (use sudo for SNMP Manager):
      cd /var/tomcat/Ticketer/bin
      ./startup.sh
Check the logs for any errors
Application has been successfully restarted and should be accessible to all users