This is a regression to JRASERVER-61328
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Problem Definition
The "connecting JIRA to SQL Server" documentations do not mention the autoCommit parameter in the JDBC URLs. This parameter is needed to prevent deadlocks as per https://confluence.atlassian.com/jirakb/deadlock-when-running-jira-with-sql-server-283640022.html and so it should be a required configuration in JIRA's dbconfig.xml.
Suggested Solution
Modify the documentation to include autoCommit=false parameter by default:
https://confluence.atlassian.com/jira063/connecting-jira-to-sql-server-2012-683541742.html
https://confluence.atlassian.com/display/JIRA064/Connecting+JIRA+to+SQL+Server+2008
Note:
Jira Server
For Jira DC it might cause issues when starting the second node as mentioned on this KB Second node fails to start due to read timed out accessing dbo.clusteredjob with MS SQL Server database
- is a regression of
-
JRASERVER-61328 Documentation for SQL Server should include setting the autoCommit parameter in JDBC URL
- Closed
- mentioned in
-
Page Loading...