Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-67647

Ability to have user session replication between the nodes in Jira Data Center (DC)

    • 14
    • 1
    • We collect Jira 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.

      When a user session is moved from one server to another, all session information is lost, including login credentials. When this happens, the user is forced to re-login in JIRA in order to create a new session.

      Please implement user session replication between the nodes in order to avoid that.

            [JRASERVER-67647] Ability to have user session replication between the nodes in Jira Data Center (DC)

            SET Analytics Bot made changes -
            UIS Original: 20 New: 14
            SET Analytics Bot made changes -
            UIS Original: 27 New: 20
            SET Analytics Bot made changes -
            UIS Original: 34 New: 27
            SET Analytics Bot made changes -
            UIS Original: 41 New: 34

            der_bran added a comment -

            4555db5a5f8f I tried to use the Redis session manager for Tomcat you suggested. At first it looked as if it worked - the details about the logged-in user were available to both cluster nodes from the shared session store. However, further tests showed that some plugins we use also store objects in the session and some of them do not implement Serializable, which leads to exceptions being thrown.

            der_bran added a comment - 4555db5a5f8f I tried to use the Redis session manager for Tomcat you suggested. At first it looked as if it worked - the details about the logged-in user were available to both cluster nodes from the shared session store. However, further tests showed that some plugins we use also store objects in the session and some of them do not implement Serializable, which leads to exceptions being thrown.
            SET Analytics Bot made changes -
            UIS Original: 34 New: 41
            SET Analytics Bot made changes -
            UIS Original: 35 New: 34
            SET Analytics Bot made changes -
            UIS Original: 28 New: 35
            SET Analytics Bot made changes -
            UIS Original: 35 New: 28
            SET Analytics Bot made changes -
            UIS Original: 42 New: 35

              Unassigned Unassigned
              lfagundes Luciano Fagundes (Inactive)
              Votes:
              130 Vote for this issue
              Watchers:
              101 Start watching this issue

                Created:
                Updated: