It was discovered that qpid-cpp was only reporting broker statistics or enforcing queue depth limits based on the size of the AMPQ 0-10 message body, instead of additionally including the header size. This caused statistics to incorrectly reflect the size of headers in the message. For example, a message with no body but many headers would not contribute to the aggregate size in bytes of a queue onto which it was enqueued. Because AMQP 1.0 messages included headers and other meta-data with the message, this issue had the potential to introduce unnecessary confusion. The size of AMQP 0-10 messages is now fixed to take the sum of the content and headers segments into account when calculating the logical size of the message. Statistics and queue limits reported or controlled in bytes now more accurately reflect the logical size of the message, and there is less difference between the 1.0 and 0-10 encodings in terms of their overall size. It is expected that queue limits will be reached earlier due to the correct logical size now being reported and enforced.
Description of problem: With AMQP 0.10 message size == size of content, but with AMQP 1.0 message size == whole (probably encoded) message. This should be unified. Also 'size' parameter of the Message object in C++ contains only the size of content. Other languages lacks the size parameter. Version-Release number of selected component (if applicable): qpid-cpp-0.22-16 How reproducible: 100% Steps to Reproduce: 1. send message via amqp 0.10 with one character content ./spout --content "A" "amqp0-10;{create: always}" 2. send message via amqp 1.0 with one character content ./spout --connection-options "{ protocol: 'amqp1.0' }" --content "A" "amqp1.0;{create: always}" 3. observe result qpid-stat -q Actual results: Queues queue dur autoDel excl msg msgIn msgOut bytes bytesIn bytesOut cons bind ========================================================================================================================= 89fbce1d-0b95-4e16-877b-b0d32876b93d:0.0 Y Y 0 0 0 0 0 0 1 2 amqp0-10 1 1 0 1 1 0 0 1 amqp1.0 1 1 0 101 101 0 0 1 Expected results: Queues queue dur autoDel excl msg msgIn msgOut bytes bytesIn bytesOut cons bind ========================================================================================================================= 89fbce1d-0b95-4e16-877b-b0d32876b93d:0.0 Y Y 0 0 0 0 0 0 1 2 amqp0-10 1 1 0 1 1 0 0 1 amqp1.0 1 1 0 1 1 0 0 1 ## OR ## Queues queue dur autoDel excl msg msgIn msgOut bytes bytesIn bytesOut cons bind ========================================================================================================================= 89fbce1d-0b95-4e16-877b-b0d32876b93d:0.0 Y Y 0 0 0 0 0 0 1 2 amqp0-10 1 1 0 101 101 0 0 1 amqp1.0 1 1 0 101 101 0 0 1 Additional info: This difference also influence others, for example limit enforcement for message sizes.