How did it lock up? Did you have someone look at the DB and determine which DB jobs were running at the time and which locks were being held? Is it possible that something else was running concurrently on the DB?
It does not seem plausible that a COM+ transaction would stay alive after the tests quit. But if the tests or application code hung while in a transaction context (for whatever reason) then we could have trouble. Jeff. -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Fred Potter Sent: Friday, January 25, 2008 2:08 PM To: MbUnit.User Subject: MbUnit Rollback & DTC Hi, Has anyone experienced database lockups from using Rollback? I'm using Rollback with a remote database - so, I have distributed transaction coordinator enabled on both ends. Everything was working fine until yesterday when the database decided to lock up, and now my coworkers on trying to blame the black magic of COM+ transactions on the database lockup. Has anyone else run into issues like this? Best, Fred --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MbUnit.User" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/MbUnitUser?hl=en -~----------~----~----~----~------~----~------~--~---
