directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Alderson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRSERVER-895) Servers refuse to replicate
Date Wed, 23 May 2007 14:41:16 GMT

    [ https://issues.apache.org/jira/browse/DIRSERVER-895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498252
] 

Martin Alderson commented on DIRSERVER-895:
-------------------------------------------

This problem is indeed caused by a message timing out.

When a message times out while the replica is marked as being in a transaction the context
is closed but the replicaInTransaction flag is only reset when a context for a _different_
replica is closed.

To fix this change "if ( !ctx.getPeer().equals( replicaInTransaction ) )" to "if ( ctx.getPeer().equals(
replicaInTransaction ) )" in org.apache.directory.mitosis.service.protocol.handler.ReplicationServerContextHandler.contextEnd.


> 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.


Mime
View raw message