Question: Message disposition disposition

[annatisch]

Hi there,

Had a quick question on expected behaviour for when a message disposition is rejected.
For example:
A message receiver returns a message, but the client takes some time to process the message before returning an 'accept' DISPOSITION. The service has declared the message expired, and therefore the DISPOSITION should be rejected to indicate that the message has been re-added to the queue for re-processing.

Is there an AMQP mechanism for this kind of behaviour? And if so, how is it handled in the library?
I've run some tests, but can see no errors/warnings in the network trace for this scenario - the DISPOSITION for the expired message seems to send without complaint (though there could be something wrong with the test if you would expect to see some error surfacing here).

[dcristoloveanu]

Hi @annatisch

I believe what you are after is the receiver settle mode "second".

2.8.3 Receiver Settle Mode
Settlement policy for a receiver.

Valid Values
0 The receiver will spontaneously settle all incoming transfers.
1 The receiver will only settle after sending the disposition to the sender and receiving a disposition indicating settlement of the delivery from the sender.

Unfortunately uAMQP does not support this now (as it was not really required by the IoT SDK where we started it.

We can discuss how it can be added.

Cheers,
/Dan