Documentation for JIRA 6.3 EAP developer (EAP) releases only. Not using this? See below:
(JIRA 6.2.x documentation | JIRA OnDemand documentation | earlier versions of JIRA)

Skip to end of metadata
Go to start of metadata

To change the default session timeout (which is 5 hours (or 300 minutes)) you must edit the file web.xml. This file can be found in <YOUR DEPLOYMENT>/WEB-INF/web.xml.

(tick) If you are deploying JIRA as a closed .war file you will need to unzip the .war, edit the file, and re-create the .war with exactly the same structure as it originally had.

The element you want to edit in the web.xml file is:

The value within the session-timeout tag defines the amount of time the session will exist, in minutes.

Note that after editing the web.xml file you will need to restart JIRA for your change to take effect.

 

User logouts

Icon

In case JIRA users are still being consistently logged out, you may need to change the context path if you are using multiple Atlassian applications on the same server. For instructions, see this Knowledge base article.

  • No labels

11 Comments

  1. Hi, is there a way to change the settings so that some checks in JIRA Integrity Checker do not time out?

    Currently a few of them are timing out.

    thanks
    Paul

  2. Can you make this session part of the regular db-based configuration? It's just annoying to have to remember to go back and change this value every time Jira is redeployed.

    http://java.sun.com/products/servlet/2.2/javadoc/javax/servlet/http/HttpSession.html#setMaxInactiveInterval(int)

    1. Amen to that!

      Do this to every other setting we might care to change, while you're at it!

      1. Ah, yeah. Let's not dig into .xml and require re-deploy just to adjust session timeout. Pretty frustrating.

  3. Anonymous

    Wow this is so much more difficult than it should be (sad)

  4. The default value appears to have changed from 30 minutes to 300 minutes at some point.

    4.0 60

    4.1 60

    4.2 60

    4.3 300

    4.4 300

    5.0 300

     

    1. Thanks very much for investigating this Matt.

      Incidentally, I've updated the equivalent pages in the JIRA 4.4.x and JIRA 4.3.x documentation too.

      Cheers,

      Giles.

  5. In JIRA 5.0.2, changing this value has no effect for the dashboard page. 

  6. Anonymous

    Chris Clifton – I'm testing this right now.  Default is 5 hours though, so it might be hard to confirm.

  7. It's not the most elegant solution but I have taken to running a set of patch files for each of the JIRA files I have edited under the install directory and made a jira_post_upgrade.sh that I run which shuts JIRA down, patches everything, and starts it back up post upgrade. it takes a bit of upfront work obviously but I have found it to be worth it in the long run.