Site announcement

We are switching off article comments on this website. Read about the upcoming changes to Atlassian Documentation.

You're visiting the Confluence Knowledge Base. Visit the Confluence Knowledge Base Home for an overview.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Symptoms

After stopping confluence via catalina.sh stop Confluence says, in the logs, that it is stopping, as below:

but the java process never terminates.

Resolution

Pass the -force parameter to catalina.sh as:

This will kill the java process and stop Confluence.

If the above results in an error, such as:

Kill failed: $CATALINA_PID not set

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

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

For Linux or Mac user:
In addition to the above, you can try a custom script that runs shutdown.sh first before sleeping 60 seconds. This script then will look inside ./id.pid to check if Tomcat process is still running. Note that this script is provided as is and not supported.

The script needs to be saved in <confluence install>/bin.

Unknown macro: {htmlcomment}

Severity: Low
Article ID: CONFKB216959212

https://support.atlassian.com/browse/CSP-35460

  • No labels