Start and Stop JIRA applications

How you start and stop your JIRA application depends on whether you are running JIRA as a Service. 

Windows

  When installed as a service...

If you installed JIRA as a service, you can Start JIRA Server and Stop JIRA Server from the Windows Start menu. 

You can't start or stop JIRA manually using the start-jira.bat and stop-jira.bat file.

  Manually when not installed as a service...

If you didn't install JIRA as a service you'll need to start and stop JIRA manually.

  • To start JIRA run <installation-directory>\bin\start-jira.bat
  • To stop JIRA run <installation-directory>\bin\stop-jira.bat

We recommend running JIRA with a dedicated user account. To do this, use use the runas command to execute start-jira.bat.

> runas /env /user:<DOMAIN>\<jira> start-jira.bat

Where <DOMAIN> is your Windows domain or computer name and <jira> is the name of your dedicated user.

  Manual start with add-ons disabled...

JIRA can be started with all non-system add-ons, or a selection of these add-ons, disabled. This helps with troubleshooting when these non-system add-ons are causing issues with your JIRA instance, such as causing JIRA to fail on start up, or when the add-on is malfunctioning and can't be removed through UPM. The parameters do not persist, that is, they are applied at start up once, and if you need to restart JIRA, you need to apply them again.

The parameters should be specified at system start up when JIRA is started using the start-jira.bat file, for example:

<installation-directory>/bin/start-jira.bat /disablealladdons /disableaddons=com.atlassian.test.plugin

If you don't use start-jira.bat for starting JIRA, but still wish to use this feature, you can add the following JVM parameter to the invocation of the servlet container that's running JIRA:

-Datlassian.plugins.startup.options="/disablealladdons /disableaddons=com.atlassian.test.plugin"

To disable multiple plugins, use a colon separated list of plugins. Regex/wildcards are not permitted, the full key of the plugin must be provided, for example:

-Datlassian.plugins.startup.options="/disablealladdons /disableaddons=com.atlassian.test.plugin:com.atlassian.another.test.plugin"

Notes

  • If the add-on key contains a space, this feature will not work, you need to manually deal with that add-on.
  • This feature does not work for JIRA Data Center applications.
  • This can be used to disable an add-on deemed critical to JIRA starting, and if one of those is disabled, JIRA will fail to start

  • This can can be used to disable JIRA application OBR bundles, for example, to stop the JIRA Software add-on:

    <installation-directory>/bin/start-jira.bat /disableaddons=com.atlassian.jira.jira-software-application

Linux 

  When installed as a service...

If you installed JIRA as a service, use one of the following commands to start or stop JIRA.

$ sudo /etc/init.d/jira start
$ sudo /etc/init.d/jira stop

You can't start or stop JIRA manually using the start-jira.sh and stop-jira.sh files.

  Manually when not installed as a service...

If you didn't install JIRA as a service you'll need to start and stop JIRA manually.

  • To start JIRA run <installation-directory>\bin\start-jira.sh
  • To stop JIRA run <installation-directory>\bin\stop-jira.sh

We recommend running JIRA with a dedicated user account:

$ su -u <user>
$ ./start-jira.sh

Where <user> is the name of your dedicated user.

If you're using Ubuntu the command is a little different:

$ sudo su <user>
$ ./start-jira.sh
  Manual start with add-ons disabled...

JIRA can be started with all non-system add-ons, or a selection of these add-ons, disabled. This helps with troubleshooting when these non-system add-ons are causing issues with your JIRA instance, such as causing JIRA to fail on start up, or when the add-on is malfunctioning and can't be removed through UPM. The parameters do not persist, that is, they are applied at start up once, and if you need to restart JIRA, you need to apply them again.

The parameters should be specified at system start up when JIRA is started using the start-jira.sh script, for example:

./bin/start-jira.sh --disable-all-addons --disable-addons=com.atlassian.test.plugin

If you don't use start-jira.sh for starting JIRA, but still wish to use this feature, you can add the following JVM parameter to the invocation of the servlet container that's running JIRA:

-Datlassian.plugins.startup.options="--disable-all-addons --disable-addons=com.atlassian.test.plugin"

To disable multiple plugins, use a colon separated list of plugins. Regex/wildcards are not permitted, the full key of the plugin must be provided, for example:

-Datlassian.plugins.startup.options="--disable-all-addons --disable-addons=com.atlassian.test.plugin:com.atlassian.another.test.plugin"

Notes

  • --disable-addons takes a colon-separated list (chosen as a colon is the only prohibited character from a plugin key) of addons to be disabled. These can be system add-ons.
  • This feature does not work for JIRA Data Center applications.
  • This can be used to disable an add-on deemed critical to JIRA starting, and if one of those is disabled, JIRA will fail to start

  • This can can be used to disable JIRA application OBR bundles, for example, to stop the JIRA Software add-on:

    ./bin/start-jira.sh --disable-addons=com.atlassian.jira.jira-software-application

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport