Uploaded image for project: 'Confluence Server and Data Center'
  1. Confluence Server and Data Center
  2. CONFSERVER-22880

Allow forced shutdown of Confluence by configuring CATALINA_PID in standalone distribution

    XMLWordPrintable

Details

    • Suggestion
    • Status: Closed (View Workflow)
    • Resolution: Won't Do
    • None
    • None
    • 2
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      This is a request to include the work around from http://confluence.atlassian.com/display/CONFKB/Confluence+Does+Not+Terminate+after+Shutdown+Script (adding $CATALINA_PID) as part of our setenv.sh

      $CATALINA_PID in setenv.sh is not a default setting in Tomcat, but perhaps it's something that we can consider for Confluence standalone?

      At the moment the challenge is to identify which directory that Tomcat can write to and know what the pid is for Confluence. Matt R mentioned that perhaps we can let Tomcat write to its /temp folder.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              rhartono Roy Hartono [Atlassian]
              Votes:
              11 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: