Configure Jira to always generate Thread Dumps on Shutdown

Context

During a critical situation where Jira is unresponsive or extremely slow, it becomes very important to capture thread dumps during the impacted period to investigate potential causes.

Many admins may not be familiar with this and restart the server before proper data is collected, losing critical information. This means that they will have to wait for another incident to occur before they can then collect proper information.

Current Behaviour

Currently, Tomcat will generate a single thread dump in the event where the shutdown process has trouble closing threads in a timely manner.

Suggestion

By default every shutdown should generate 3 thread dumps, 5 seconds between. To extend this it can also have an easy method to disable this behaviour.