Is it safe to terminate stuck DB transactions of Confluence?

What is the best way to deal with too long database transactions in Confluence?

Periodically we have situations when some page/attachment updates fail and DB locks stay for an hours held by additional background threads. Is 15 minutes enough for average Confluence query to its own DB? Is it good practice to terminate longer transactions forcibly?

This way we release DB locks and close waste threads that sometimes overconsume CPU resources.

1 answer

1 accepted

This widget could not be displayed.

Hi Oleksiy,

You could specify database query timeout that will automatically terminate database queries which took longer than the specified timeout.

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Published Tuesday in Confluence

Add-on evaluation with confluence templates

Atlassian market place contains number of Apps/Addons which improves the capability of out of the box Atlassian products. It is good to follow a plugin evaluation process before install add-ons. So t...

105 views 12 6
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you