0

I'm currently working on a project that uses EventStore, CommonDomain, and NServiceBus, when I have NumberOfWorkerThreads set to 1, all of our services(nservicebus - we have 6 of them, each has thier own event store) runs perfectly, but when i set NumberOfWorkerThreads to more than one, I start seeing a ton of deadlocks, i mean like at least 50 per minute. All of the deadlocks are on the Commits table. From what i've found is that, it looks like I'm updating the same aggregate in multiple threads, which could easily happen during and import of a catalog per say, and I update quantity in one thread, while updating the price in another thread, so both threads are trying to update the same aggregate.

Has anyone else had this issue, and how have you gotten around it?

Ruben Bartelink
  • 59,778
  • 26
  • 187
  • 249
no1ross
  • 55
  • 5
  • I imagine you're using a SQL database for the storage. What transaction isolation level are you using? – Jonathan Oliver Apr 05 '12 at 16:58
  • Hi Jonathan, Thanks for the response, we are using the default setup, not sure about the Transaction isolation level, as i have not modified your code at all. I've also tried to use RavenDb as well, and it throws a ton of concurrency errors. – no1ross Apr 05 '12 at 18:39
  • @no1ross - have you found a solution? I'm facing the same issue with SqlAzure. – Jakub Konecki Nov 09 '12 at 23:06

0 Answers0