[ 
https://issues.apache.org/jira/browse/QPID-7504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15653539#comment-15653539
 ] 

Keith Wall commented on QPID-7504:
----------------------------------

http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-messaging-v1.0-os.html#section-message-format

In AMQP 1.0 "the body consists of one of the following three choices: one or 
more data sections, one or more amqp-sequence sections, or a single amp-value 
section".  One issue that must be consider is how the WMC should handle a 
message with multiple data sections, or AMQP values/sequences.

> Operator cannot download application message content for AMQP 1.0 messages
> --------------------------------------------------------------------------
>
>                 Key: QPID-7504
>                 URL: https://issues.apache.org/jira/browse/QPID-7504
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>            Reporter: Keith Wall
>             Fix For: Future
>
>
> The Web Management Console gives the user the ability to download the 
> message's content.  This is especially useful for messages whose payload is a 
> file (say a PDF).  As an operator, he can download the content and verify 
> that the message is as expected.
> This feature work for AMQP 0-8..0-10 messages, but not for AMQP 1.0 messages. 
>  In the AMQP 1.0 case, current the 'message content' is the concatenation of 
> the immutable sections of the AMQP message (i.e. includes the application 
> headers).  The operator has no reasonable way to get the the application's 
> payload.
> Also, the message size reported by the console is 'wrong' in the AMQP 1.0 
> case.  It does not report the size of the application's payload, but the 
> combined size of the immutable sections.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to