We are running some load tests in our PT environment and are regularly able to reproduce the outcome of having multiple orphaned transactions. I am not sure how to narrow down the cause. We are running SQL 2K8 on Win Server 2008 R2 cluster with
JDBC / XA (.dll version 3.0.x). I'm not sure what additional information would be helpful, so please feel free to ask for whatever you need to assist.
In looking at sys.syslockinfo and sys.dm_tran_locks, I can determine that these orphaned transactions are blocking all requests against two specific tables and can see the locks that the orphaned transactions have on those two tables. Is there any
way I can identify what is going on to cause the orphaned transactions?
Any assistance on this would be greatly appreciated.
View Complete Post