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
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#messageSent,
ReplicationClientContextHandler#messageReceived and
ReplicationClientContextHandler#beginReplication (which only begins replication
if there are no unacknowledged messages).
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 which
expect replication to succeed within a few seconds.
When this issue is fixed ReplicationServiceITest#testTwoWayBind should be
re-enabled.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
