[ https://issues.apache.org/jira/brow...ls:all-tabpanel ]

Emmanuel Lecharny updated DIRSERVER-998:
----------------------------------------

Fix Version/s: 1.5.1

> Messages time out if acknowledged too quickly
> ---------------------------------------------
>
>                 Key: DIRSERVER-998
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-998
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: mitosis
>    Affects Versions: 1.5.0
>            Reporter: Martin Alderson
>            Priority: Minor
>             Fix For: 1.5.1
>
>
> Every so often a message (a login or logEntry message) will be written to a peer (
by a 'client') and an acknowledgement is sent back before the sender knows that the 
original message has been sent.  We do not allow any more messages to be sent until 
the
last sent message has been acknowledged or has timed out (which takes 60 seconds by default)
.
> In the code, the points of interest are  ReplicationClientContextHandler#messageS
en
t,  ReplicationClientContextHandler#messageR
eceived and ReplicationClientContextHandl
er#beginReplication (which only begins replication if there are no unacknowledged me
ssa
ges).
> This isn't a major problem as replication will continue after the message 
has timed out, but it slows things down and is especiually bad for tests whi
ch expect replication to succeed within a few seconds.
> When this issue is fixed ReplicationServiceITest#testTwoWayBind should be re-enabl
ed.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[ Post a follow-up to this message ]