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.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
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...
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