[
https://issues.apache.org/jira/browse/DIRSERVER-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100245#comment-13100245
]
Kiran Ayyagari commented on DIRSERVER-1655:
-------------------------------------------
This delay of events can happen at any level before reaching the replication
interceptor, IMO the best is to let the journal keep them in sorted order (and
currently this CSN based sort order is maintained in the existing JDBM based
journal implementation)
> 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
