With Atlassian applications there are typically 2 places where you can set timeouts. The first is within Tomcat itself. The second is in your proxy. I contend that timeouts are misunderstood and as a result, misconfigured.
From the Tomcat Connector Docs:
If JK aborts waiting for a response, because a reply timeout fired, there is no way to stop processing on the backend. Although you free processing resources in your web server, the request will continue to run on the backend - without any way to send back a result once the reply timeout fired.
For your proxy, since it has no way to kill a backend job, it also does essentially the same thing.
But what does this mean for us practically? I think it's easier to illustrate with an example:
This is of course an extreme example, but in practice this kind of thing does happen. Especially across a variety of users and operations. Most importantly, the timeout in this case is not bringing any value to end users, and especially not to application administrators.
I propose that unless you have a very good reason to specify low timeouts that you set them exceptionally high.
I would love to hear counterpoints that I may not have thought of.
Hi Atlassian community, My name is Max and I work on the product integration team at Atlassian. I am pleased to announce the early access program for the Jira Cloud add-in for Outlook. This add-in...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events