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.
|Field||Original Value||New Value|
|Fix Version/s||0.11 [ 12316272 ]|
|Fix Version/s||0.9 [ 12315382 ]|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Status||In Progress [ 3 ]||Ready To Review [ 10006 ]|
|Assignee||Andrew Kennedy [ andrew.kennedy ]||Rafael H. Schloming [ rhs ]|
|Assignee||Rafael H. Schloming [ rhs ]||Robbie Gemmell [ gemmellr ]|
|Status||Ready To Review [ 10006 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|