[DIRSERVER-998] Messages time out if acknowledged too quickly

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.5.0
• Fix Version/s: 1.5.1
• Component/s: replication
• Assignee: Martin Alderson
• Reporter: Martin Alderson
• Created: 15/Jul/07 19:37
• Updated: 18/Aug/07 15:59
• Resolved: 01/Aug/07 20:56

Description

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.