JIRA Transaction Deadlock

In our Dev environment we can see in the logs says "Transaction (Process ID 51) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction" and JIRA is not loading. what is the problem ?

1 answer

1 accepted

0 vote

You are using MS-SQL and have not configured it correctly.  Go back over https://confluence.atlassian.com/adminjiraserver071/connecting-jira-applications-to-sql-server-2008-802592183.html#ConnectingJIRAtoSQLServer2008-2.CreateandConfiguretheSQLServerDatabase and make sure you have set the "read committed snapshot" to "on"

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Feb 15, 2018 in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

1,210 views 6 19
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot