Jan. 31st, 2012

billroper: (Default)
The automated testing uncovered a number of glitches in the locking fixes which I've been busily patching. While I was in the process of trying to convince a particular set of transactions that, no, they did not need to grab a write lock on the cube object and hold it for several minutes, thereby preventing a bunch of other processes from running successfully, I discovered that the code that does check out locks for our documents was never properly locked.

Oh. Well, that would explain that class of error that I saw.

I'm now in a detour as I move the check out lock interfaces into a class where we can lock them granularly by entity and where you'll have to take a write lock on the entity to be able to get at them. I see the main road in the distance...

Profile

billroper: (Default)
billroper

June 2026

S M T W T F S
  1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 1617181920
21222324252627
282930    

Most Popular Tags

Page Summary

Style Credit

Expand Cut Tags

No cut tags
Page generated Jun. 17th, 2026 03:44 pm
Powered by Dreamwidth Studios