7.3.4.8.2 UADP states:

If the encoded AMQP message size exceeds the Broker limits it shall be broken into multiple chunks as described in 7.2.2.2.4.

For JSON this behavior is not defined.

Discussed in Telco:
2.6.14 in AMQP spec
This should refer to ‘max-message-size’ in the AMQP spec.

It is very hard to be implemented because the Pub/Sub implementation is generic so it is not AMQP aware. Chunk generation should be underlying protocol responsibility. In this case, we can use native AMQP feature: more flag of the transfer performative.

Anyway, we will try to implement it.

max-message-size < AMQP overload + UADP chunk.

Current AMQP overload is not exposed by the AMQP implementation API ?!

How to deal with it?
Is there any implementation that can be recognized as the proof of concept.

Extended the relevant paragraph in 7.3.41 to the following text:
This specification defines two possible message mappings for the AMQP message body, the UADP message mapping defined in 7.2.2 and a JSON message mapping defined in 7.2.3. AMQP Brokers have an upper limit on message size. The limit is defined by the AMQP field max-message-size. The mechanism for handling NetworkMessage that exceed the Broker limits depends on the MessageMapping. For MessageMappings that support chunking, the NetworkMessage shall be broken into multiple chunks. The chunk size plus the AMQP header should not exceed the AMQP max-message-size. For MessageMappings that do not support chunking, the NetworkMessages exceeding the maximum size mut be skipped. Diagnostic information for such error scenarios are provided through the Events of the type PubSubTransportLimitsExceedEventType defined in 9.1.12.2 and through the FailedTransmissions counter of the PubSubDiagnosticsWriterGroupType defined in 9.1.11.9.

Agreed to changes in UA face to face meeting - will be available in draft 1.05.02
Needs errata

Agreed to 1.04 Errata.