this bug has cost us many hours of labor and hasnt been fixed yet! did you ever get the problem again or fix it?
Ben
· 3 years ago
We never discovered the true source of the bug, but also haven't had it reoccur. We tidied up some of the code in the DB-intensive section of the system to reduce deadlocks (selecting from the same table that another thread is trying to write to), and also increased the performance of the database server.
All Comments
In combination they seemed to resolve the issue.