[QPID-5828] qpid::Messaging API Sender/Receiver assorted bugs

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.28
• Fix Version/s: 0.29
• Component/s: C++ Client
• Assignee: Gordon Sim
• Reporter: Clive Lilley
• Created: 16/Jun/14 15:24
• Updated: 28/Apr/16 11:14
• Resolved: 25/Jun/14 14:56

Description

Several issues with the qpid::messaging::Sender and qpid::messaging::Receiver implementations.

Summarized below:

• TTL on a message does not get adjusted when stored in the outgoing
  Sender queue and the queue cannot be emptied due to broker unavailability.

• TTL on messages that expire while they are cached in the receivers queue. Messages still get delivered even though they have expired.

• getUnsettled segmentation error when called with no connection to
  broker but messages in the Sender outgoing queue (fine with zero size
  outbound queue).

• Inconsistent behavior of Sender when Broker not connected. When
  sending a message an Exception occurs, as no connection, but messages
  are still placed in outbound queue up until the Sender is flushed
  ('window < Capacity/4' , not sure where the 4 comes from). At this point
  any further sent messages still cause an exception, but messages do not
  get placed in the outbound queue. Varying the capacity varies when this
  occurs and so doesn't seem correct.