ResolutionĬonfigure your database to use the isolation level, Read Committed with Row Versioning. If you raise a support issue, please include the SQL Server logs in addition to your support zip/Confluence logs. It also provides an explanation for interpreting the output, which may help your troubleshooting process. This MSDN blog outlines the process and gives examples of the output this additional level of trace logging provides. You can enable a trace flag on SQL Server that will log deadlocked queries with enough verbosity to confirm if there is an issue with the type of lock that is being used. If the symptom reflects the variant above, Tracking Plugin might have been installed in Confluence. SQL Server is escalating row locks (in this case deleting a draft from the CONTENT table) to table locks and stopping other transactions from accessing the table. It's also possible for this to happen without putting anything into the logs at all. Rerun the transaction.Īt .SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368) Rerun the transaction.Ĭaused by: : Transaction (Process ID 51) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Transaction (Process ID 51) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. : Hibernate operation: could not update: SQL ] log rvice() for servlet file-server threw exception Rerun the transaction.Īt .SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:367) Rerun the transaction.Ĭaused by: : Transaction (Process ID 55) was deadlocked on lock resources with another process and has been chosen as the deadlock victim.
nested exception is : Transaction (Process ID 55) was deadlocked on lock resources with another process and has been chosen as the deadlock victim.
: Hibernate operation: could not delete: SQL Transaction (Process ID 55) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. url: /confluence/pages/docreatepage.action | userName: tstcreator3 The column heading for the trace flag number is either Global or Session, depending on whether you are checking the status for a global or a session trace flag. This indicates whether the trace flag is ON (1) or OFF (0). nested exception is : Transaction (Process ID 55) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. DBCC TRACESTATUS returns a column for the trace flag number and a column for the status. 17:01:21,359 ERROR onThrowable Invoking rollback for transaction on action '/pages/docreatepage.action (CreatePageAction.doAdd())' due to throwable: : Hibernate operation: could not delete: SQL Transaction (Process ID 55) was deadlocked on lock resources with another process and has been chosen as the deadlock victim.
0 kommentar(er)
