[
https://issues.apache.org/jira/browse/DIRSERVER-895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498290
]
Martin Alderson commented on DIRSERVER-895:
-------------------------------------------
Hi Alex,
I would be interested in knowing what critical flaws the current system has
aside from the ones listed in this tracker. I think I have found another
couple of issues myself but I need to make sure they were not my doing before I
report them.
I am attempting to use the replication module (I've branched it for now so I
can mold it into something I can use) in a specific project I am working on.
I'm not entirely sure why it would need to be completely rewritten - the basic
architecture seems reasonable to me. Obviously it is not production ready yet
but isn't it just a case of rigorously testing it and fixing the problesm as
and when they occur?
I can continue this discussion elsewhere (the dev mailing list?) if you want by
the way.
> 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.
