[
https://issues.apache.org/jira/browse/DIRSERVER-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728694#action_12728694
]
Emmanuel Lecharny commented on DIRSERVER-1377:
----------------------------------------------
After days of painfull debug sessions, code analysis and log grepping, we have
moved the serialization in the backend (JDBM), synchronized correctly
JdbmStore, and it seems to have a positive impact.
I've run some test, and was able to inject more than 1 400 000 updates without
any problem.
But the oneLevelIndex is still corrupted, we have to understand why.
The idea is to replace the AVLTree by a simple array, which will be sorted. It
should be a bit less expensive in CPU, will suck less memory, and cost more for
updates.
This is what I'm on right now.
> 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.
