Client re-enqueue a packet that causes PAYLOAD_LIMIT_EXCEEDED disconnect event.

[chapost1]

Describe the bug

Client keeps retrying publish message (re-enqueue) post disconnect, which it's cause is PAYLOAD_LIMIT_EXCEEDED.
which cause infinite connect/disconnect events.

Expected Behavior

Result with a puback that indicates a failure and not re-enqueue the message as it's payload won't shrink.

Current Behavior

1. Client attempts to publish a message with payload larger than AWS max payload size.
2. Client disconnects.
3. Client re-connects.
4. Client re-enqueue packet, and try to send it.
5. Client disconnects.
6. Client re-connects.
7. Client re-enqueue packet, and try to send it.
8. ...

No PUBACK response for the publish method.

Reproduction Steps

Just create a client instance that connects post disconnect events, and attempt to publish a message with payload larger than allowed size.

Possible Solution

Not sure if feasible, because if no puback is returned, then maybe it's on the iot-core service side also, but I think the solution should behave with resulting with failure puback or at least not re-enqueue as it will not be resolved by itself.

Additional Information/Context

No response

SDK version used

1.20.0

Environment details (OS name and version, etc.)

ubuntu:22.04

[jmklix]

Can you try using the MQTT5 client? It will handle the PAYLOAD_LIMIT_EXCEEDED, because part of the updated protocol included the server communicating that the payload limit is.