Affects Version/s: 5.13.19
Fix Version/s: 5.13.21
Datasource - Jira REST
Jira Data Center
- Configure a field connected to Jira REST API
- Edit the field
Options are not retrieved, the query fail
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 :
A typical trace initiated by a browser client (we can see the node ID as prefix in JSESSIONID cookie) :