Description
We do use lock for read and write in the OperationManager, which might be a problem. The rational is that we may have to combine some reads and writes in the very same operation (for instance, if we update some of the opAttributes, or if we update ore than one entry).
I'm not sure this is needed, and I'm not sure we can't find another way to protect the server against concurrent modifications.
In any case, a thorough evaluation of those lock usage must be done.