Big sized messages and settled_mode about azure-uamqp-c

[dcristoloveanu]

Hi @ndanzi,

Setting sender_settle_mode_settled means that the transfers are considered by the sender to be settled.
AMQP spec section 2.8.2 states:

2.8.2 Sender Settle Mode
Settlement policy for a sender.





Valid Values
0 The sender will send all deliveries initially unsettled to the receiver.
1 The sender will send all deliveries settled to the receiver.
2 The sender MAY send a mixture of settled and unsettled deliveries to the receiver.

This literally means that the receiver will not report the state of the delivery as it is considered settled.

If you do want to have the delivery state be considered unsettled until the receiver confirms it as such please use the unsettled mode in the enumeration.

I would like to look a big deeper though on what happens on the server side.
Can you please provide some more details on:

The sample code you run as server.
The client code you run.
If possible can you please turn on logging and post the logs here?
Also if you could give me the commit Id you used for uamqp that will help in reproducing and making sure the issues gets fixed.

To turn on logging:

connection_set_trace(connection, true);

in your samples?

Thanks,
/Dan

[ndanzi]

Thank you for the reply.

I mistakenly got it backwards: with unsettled mode now actually the client fails sending the message.
In this way I am able to catch the delivery state of the message.

For uamqp I used the Release 2016-11-17 with some paches (in order to make it work on windos ce 6.0).
I also applied the fixes of Address Issue #24: default values for fields if they are NULL and hav… and Fix fields that are nmot defaulted by the generator in order to fix i…
As a client I run the message_sender_sample provided in the samples.

The limitations on server side are due to the free account which limitates the incoming message by size

Thanks
Nicolò