Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.

Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Still not shutting down properly?

1. If the above results in an error, such as:

   Kill failed: $CATALINA_PID not set
   

   Add the following line of code to the top of your <JIRA-Installation-Directory>/bin/setenv.sh file (Standalone instance):

   CATALINA_PID="<Change this to your preferred location>/id.pid"
   export CATALINA_PID
   

   Tomcat will automatically write its process id to id.pid in your specified path and kill its process with the -force parameter.

2. In addition to the above, you can try a custom script that runs shutdown.sh first before forcing Tomcat to shutdown. This script will sleep 60 seconds then look inside ./id.pid to check if Tomcat is still running. If Tomcat is still running, it will issue a catalina.sh stop -force.
3. Also, here you can find a script which forces the application to shutdown and deletes the lock file in the application home directory. It will look inside ./id.pid for the process ID and run catalina.sh stop -force for that process.
   Both scripts need to be saved in <JIRA install>/bin and assume id.pid is located in the same location.