We have developed a tool that interacts with JIRA and Confluence for creating Confluence pages for JIRA issues, and then linking the JIRA issue to the Confluence page. All of this is done over the REST APIs for JIRA and Confluence.
When the JIRA REST API responds to our calls, it works as expected. However, when a large-ish amount of time passes (so far it has appeared when consecutive calls are separated by an hour or more), the JIRA REST API will return an error that we cannot connect. Attempting to re-query a few times (on error) eventually results in the service responding as expected.
It sounds almost like a session timeout, but we are connecting to the REST API using basic authentication, providing username and password for each request. And we're not using a session token or OAuth token or anything for successive requests.
That leads me to believe that the service for the REST API may be spinning down/going to sleep/going idle after a certain amount of time, and then waking back up once we start poking it with requests.
1. Does anyone know for certain if the REST API service goes idle?
2. If so, does anyone know how to keep it from doing so?
3. If not, has anyone else experienced this issue and have a solution they could share?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs