[
https://issues.apache.org/jira/browse/DIRSERVER-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722581#action_12722581 ]
Emmanuel Lecharny commented on DIRSERVER-1377:
----------------------------------------------
After some more investigations, the problem is narrowed to the JdbmTable.put(K, V) operation, not necessarily on the oneLevelIndex (but most often on this index).
A possible bug in JDBM ?
At this point, I see no other option than to remove all the surrounding code and do a direct tester on the index. It will be faster to determinate what can be the problem...
> Potential concurrency issue when adding/modifying/deleting entries at a high rate
> ---------------------------------------------------------------------------------
>
> Key: DIRSERVER-1377
> URL:
https://issues.apache.org/jira/browse/DIRSERVER-1377> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.4
> Reporter: Emmanuel Lecharny
> Priority: Blocker
> Fix For: 1.5.5
>
>
> When adding/deleting entries with many clients (a client add and delete an entry many times), we may have some concurrency problem, as the index are updated without concurrent acces protection.
> Synchronizing the classes where we update the index might help.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
