[jira] [Commented] (QPID-7823) [Java Broker] [AMQP1.0] Contradicting message-formats on multi transfer deliveries should result in error

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (QPID-7823) [Java Broker] [AMQP1.0] Contradicting message-formats on multi transfer deliveries should result in error

JIRA jira@apache.org

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

ASF subversion and git services commented on QPID-7823:
-------------------------------------------------------

Commit 322760c7cfb81f9e85ac0af8f93c481ab849a702 in qpid-broker-j's branch refs/heads/master from [~lorenz.quack]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=322760c ]

QPID-7823: [Java Broker] Add failing test (currently ignored) demonstrating this JIRA.


> [Java Broker] [AMQP1.0] Contradicting message-formats on multi transfer deliveries should result in error
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-7823
>                 URL: https://issues.apache.org/jira/browse/QPID-7823
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>            Reporter: Lorenz Quack
>
> The AMQP specification states in [section 2.7.5|http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transport-v1.0-os.html#type-transfer] about the message-format field of the Transfer performative:
> bq. This field MUST be specified for the first transfer of a multi-transfer message and can only be omitted for continuation transfers. It is an error if the message-format on a continuation transfer differs from the message-format on the first transfer of a delivery.
> We currently do not enforce this. Currently we just take the value of the first transfer that specifies it and ignore all subsequent values which is not spec compliant. We also allow it to be unspecified (i.e., null) in which case we default to UnsignedInteger(0).
> [AMQP-130|https://issues.oasis-open.org/browse/AMQP-130] was raised to clarify how to handle the error case.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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