Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Timeouts, how long, and why do we use them

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:

  1. User exports a large number of issues from Jira
  2. Timeout kills the connection before the user receives their results
  3. The export continues to run in the background utilizing JVM resources
  4. User sees this as a failure and goes back to #1
  5. We now start building up more and more of a backlog of running jobs

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.

1 comment

What would be an "exceptionally high" timeouts in your opinion? I normally just leave the default timeout for tomcat.

I tend to set it anywhere from 10-30 minutes.

When the timout is long, the user get impatient and refresh the browser. That would also build up more running job on the server right? I noticed that user tend to refresh their browser after 3-4 minutes.

This is a possibility, but with a timeout, it is a certainty. I prefer the prior 🤷


Log in or Sign up to comment