Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.9
-
None
Description
The 0-10 AMQP protocol implementation sends a SessionComplete command with an empty RangeSet, which will be replied to with a SessionKnownComplete and a similar empty or null RangeSet (these are equivalent on the wire) iff the TimelyReply field is set to true in the request.
I think that the initial empty SessionComplete (caused by a call to flushProcessed normally) should never be sent, so adding a check for range.size() > 0 before sending should do this.