Force Jira to use nolock

unknown

Using Jira 5.2.6 and MS SQL 2008

Our DBA team has reported that we're getting a lot of locked SPIDs. They've requested that we add nolock to our sql calls. We have already added autoCommit=false to our db string and we are still getting a lot of deadlocks and locked SPIDs.

Is there any way to force Jira to use nolock and/or any other suggestions?

John Garcia

Generally, we do consider nolock to be a risky mode to operate in, so we always recommend AGAINST using it for Production applications. In fact, most of our products will verify that the database and its tables are in the READ COMMITTED mode prior to starting. That said, JIRA is generally very good at managing its connection pool, and we've only seen problems when a plugin ties up one of the connections and refuses to release it.

For more info, please review this Stack Overflow thread: http://stackoverflow.com/a/1453000/2759475