[
https://issues.apache.org/jira/browse/DIRSERVER-895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498293
]
Emmanuel Lecharny commented on DIRSERVER-895:
---------------------------------------------
Hi Martin,
the current replication system we have is very basic, and won't support the
extended features we want it to support in the near future. This is why we want
to rewrite it completely.
However, you can use it, and we can apply the patches you are submitting.
We are also interested in feedbacks because they will help us to see which kind
of problems we have with the current replication system (nothing is better than
real life usage ...)
Ultimatly, we are *really* interested in having more people involved in the
rewrite we are planning, because it will be hudge and complex. So feel free to
join us !
> Servers refuse to replicate
> ---------------------------
>
> Key: DIRSERVER-895
> URL: https://issues.apache.org/jira/browse/DIRSERVER-895
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: mitosis
> Affects Versions: 1.5.0
> Reporter: Martin Alderson
>
> It is possible for a server to get itself in a state where it will never
> accept replication logs from other servers until it is restarted.
> I encountered this while debugging but I believe it must be possible to get
> in this state during normal execution.
> It seems that there is a case where a server starts a replication transaction
> (sets ReplicationServerContextHandler#replicaInTransaction) but fails to
> notice that it has ended (perhaps due to a message timeout?)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
