[
https://issues.apache.org/jira/browse/DIRSERVER-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100262#comment-13100262
]
Emmanuel Lecharny commented on DIRSERVER-1655:
----------------------------------------------
IMO, it's not enough to rely on the fact that the journal is sorted, because
CSN are not consecutive. We really need to guarantee that the modifications
stored in the log are consecutive.
One solution could be to add a transient field in the CSN clas,s containing the
order of creation (incremented by the CsnFactory).
> Possible incorrect insertion of modifications in the consumer log
> -----------------------------------------------------------------
>
> Key: DIRSERVER-1655
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1655
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 2.0.0-M2
> Reporter: Emmanuel Lecharny
> Priority: Critical
> Fix For: 2.0.0-M4
>
>
> The way we process modifications in the EventInterceptor, creating a new
> thread, make it possible that the modifications may be inserted into a
> consumer log in the wrong order.
> A possoble solution could be to use the same thread to insert modifications
> in the log.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
