Vault deadlock error

This forum is now locked, since Gold Support is no longer offered.

Moderator: SourceGear

Locked
christian
Posts: 202
Joined: Tue Sep 14, 2004 1:02 pm
Location: UK

Vault deadlock error

Post by christian » Wed Mar 09, 2005 4:21 am

We just received this from the RSS feed against a Vault database:

System.Data.SqlClient.SqlException: Transaction (Process ID 54) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
at System.Data.SqlClient.SqlDataReader.Read()
at VaultServiceAPILib.VaultServiceAPI.BeginVersionHistoryQuery(Int32 nRepID, Int32 nUserID, Int32 nRowLimit, Int64 nObjID, DateTime dtBeginRange, DateTime dtEndRange, Int64 nStartVersion, Int32& nRowsRetrieved, VaultIntHistoryQuery& vihq)
at VaultService.VaultWeb.WebCommon.GetTxHistory(HttpSessionState hss, Int32 repid, Int64 rootid, Int32 days, VaultTxHistoryItem[]& items, VaultTxDetailHistoryItemColl[]& details)
at VaultService.VaultWeb.rss2.Page_Load(Object sender, EventArgs e)

at System.Data.SqlClient.SqlDataReader.Read()
at VaultServiceAPILib.VaultServiceAPI.BeginVersionHistoryQuery(Int32 nRepID, Int32 nUserID, Int32 nRowLimit, Int64 nObjID, DateTime dtBeginRange, DateTime dtEndRange, Int64 nStartVersion, Int32& nRowsRetrieved, VaultIntHistoryQuery& vihq)
at VaultService.VaultWeb.WebCommon.GetTxHistory(HttpSessionState hss, Int32 repid, Int64 rootid, Int32 days, VaultTxHistoryItem[]& items, VaultTxDetailHistoryItemColl[]& details)
at VaultService.VaultWeb.rss2.Page_Load(Object sender, EventArgs e)


Is this serious?
Thanks
Christian

jclausius
Posts: 3702
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Wed Mar 09, 2005 9:03 am

No. This error is telling you the history query failed.

What version of Vault server is this being used against?
Jeff Clausius
SourceGear

christian
Posts: 202
Joined: Tue Sep 14, 2004 1:02 pm
Location: UK

Post by christian » Fri Mar 11, 2005 10:39 am

Server Version 3.0.2

jclausius
Posts: 3702
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Fri Mar 11, 2005 10:46 am

OK. I'll log a request to take a look at the RSS feed.

My instincts are telling me the RSS feed does a long history query on $/. So, it is possible SQL Server considered this a problem (chose it as a deadlock victim), while someone else was in the middle of committing a transaction.
Jeff Clausius
SourceGear

Locked