Emmanuel Lecharny created DIRSERVER-1832:
--------------------------------------------
Summary: Rethink the use of lock in the OperationManager
Key: DIRSERVER-1832
URL: https://issues.apache.org/jira/browse/DIRSERVER-1832
Project: Directory ApacheDS
Issue Type: Improvement
Affects Versions: 2.0.0-M11
Reporter: Emmanuel Lecharny
Fix For: 2.0.0-RC1
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
