I get deadlocks and the wiki states, that one has to SET IMPLICIT_TRANSACTIONS ON: https://confluence.atlassian.com/display/JIRAKB/Deadlock+when+running+JIRA+with+SQL+Server
But it seems this doesn't persist. How can I make that setting permanent in SQLServer?
EDIT: It is impossible to set that option at db level. It's only possible to set it as defaults for all users of the whole instance (i.e. server):
http://msdn.microsoft.com/en-us/library/ms190707(v=sql.90).aspx
http://msdn.microsoft.com/de-de/library/ms176031(v=sql.105).aspx
One needs to configure the database in dbconfig.xml in the jira home directory and append ";autoCommit=false" to the url:
<url>jdbc:jtds:sqlserver://localhost:1433/jiradb;autoCommit=false</url>
http://sourceforge.net/p/jtds/patches/109/
That's a MS-SQL Server question really. Start at http://msdn.microsoft.com/en-us/library/ms187807.aspx
Of course I did read that page before asking here.
And from all I read, I still think, that the described solution is wrong and that the setting is session-only and as such only useful if issued by the application (JIRA) itself.
No, that's the point - it's a database server setting, NOT the application.
The application could do it with the session, but then it would need more rights over the database than it needs for day-to-day running, and you'd have to do database specific coding. (i.e. bad security practice and bad coding practice)
I would agree with you, if it was possible to set that option permanently.
But sadly this isn't possible. Even Atlassian support got this wrong and replied with this article:
http://blog.techdreams.org/2007/11/implicit-transactions-onoff-sql-server.html
Which clearly says:
"5. [...] from now onwards all the new connections opened through Management Studio/Workbench starts an implicit transactions"
Yes, it was a configuration in Atlassian's config files ;-)
Anyway, you can't deny that all documentation on Atlassian's side about that problem is wrong, even the (initial) support.
BTW: Thanks to Richie Gee [Atlassian] for investigating and finally solving that issue.
Ah, good, you found it - set it for the user. Not an application setting then, and nothing to do with the code.
Yes, a server setting in a config file, I know.
Atlassian support are very good, all credit to them :-)
It looks like you're new here. Sign in or register to get started.
