[
https://issues.apache.org/jira/browse/DIRSERVER-895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Alderson resolved DIRSERVER-895.
---------------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.5.2)
1.5.1
Assignee: Martin Alderson
If a connection is closed during a replication transaction (which could be due
to a flakey connection or a message timeout etc) this bug would have cropped
up. Applied the patch mentioned earlier.
> 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
> Assignee: Martin Alderson
> Fix For: 1.5.1
>
>
> 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.
