Uploaded image for project: 'Elements Connect'
  1. Elements Connect
  2. CO-3499

nFeed does not always retrieve options when connected to Jira REST API - Data Center

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: 5.13.19
    • Fix Version/s: 5.13.21
    • Labels:
      None
    • Functional components:
      Datacenter
      Datasource - Jira REST

      Description

      How to

      Jira Data Center

      • Configure a field connected to Jira REST API
      • Edit the field

      Current

      Options are not retrieved, the query fail

      Expected

      It works

      Hints

      I took a trace at load balancer level and analysed the http headers sent by nFeed in its REST requests.
      I found that the JSESSIONID cookie is not prefixed with the node ID as it should be. As a consequence, the load balancer forwards the requests to any available node, we have one chance among two to go a node that doesn't know this JSESSIONID.

      A typical trace for a REST call initiated by nFeed :

      GET /rest/api/2/project/$issue.customfield_13002/ HTTP/1.1
      Host: xxxxx.xxx.xxx.xxxxx
      Cookie: JSESSIONID=7164EA0BA99053F771EBAB023095C4E1
      

      A typical trace initiated by a browser client (we can see the node ID as prefix in JSESSIONID cookie) :

      GET /secure/MyJiraHome.jspa HTTP/1.1
      Host: xxxxx.xxx.xxx.xxxxx
      Cookie: JSESSIONID=node1~29EDC51AD7EF755A2BB91D31A71A42B4
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                christophe.prome@valiantys.com Christophe Promé
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: