qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-7748) [Java Broker] In AMQP 1.0 ensure we send Flow echo in a timely fashion
Date Thu, 11 May 2017 13:23:04 GMT

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

ASF subversion and git services commented on QPID-7748:

Commit c94d60e31817a68413905b398f03a4d4cc9adec5 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=c94d60e ]

Revert "QPID-7748: [Java Broker] Remove superfluous SequenceNumber"

This reverts commit 5017eb060c30a1b6d265defa17ad7b798c2f2f12.
The difference in the compareTo method between SequenceNumber and
UnsignedInteger prohibits the removal of the former.

> [Java Broker] In AMQP 1.0 ensure we send Flow echo in a timely fashion
> ----------------------------------------------------------------------
>                 Key: QPID-7748
>                 URL: https://issues.apache.org/jira/browse/QPID-7748
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>            Reporter: Lorenz Quack
>             Fix For: qpid-java-broker-7.0.0
> Currently, it seems that when the broker receives a AMQP 1.0 Flow performative with {{echo=True}}
we are not always sending back a Flow performantive in a timely fashion.
> The spec says (2.7.4)
> bq. If set to true then the receiver SHOULD send its state at the earliest convenient
> This was braught out by the Protocol test {{org.apache.qpid.tests.protocol.v1_0.transport.link.FlowTest#echoFlow}}.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message