qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Broadstone (JIRA)" <j...@apache.org>
Subject [jira] [Created] (QPID-6826) transfer frame message-format is required to be 0
Date Tue, 03 Nov 2015 22:08:27 GMT
Matt Broadstone created QPID-6826:

             Summary: transfer frame message-format is required to be 0
                 Key: QPID-6826
                 URL: https://issues.apache.org/jira/browse/QPID-6826
             Project: Qpid
          Issue Type: Bug
          Components: C++ Broker
    Affects Versions: 0.32
            Reporter: Matt Broadstone
            Priority: Minor

I work on an node AMQP 1.0 module (https://github.com/noodlefrenzy/node-amqp10), and we recently
discovered a bug that prevented us from communicating properly with Azure EventHub over AMQP
1.0 because we were sending a `null` value for the message-format of a transfer frame. I also
run a number of integration tests against qpidd (and use qpidd for a product), and realized
that this has never been an issue. The specification indicates that the message format described
in the spec (section 3.2) is defined as message format 0.

This isn't a big bug (perhaps it isn't even a bug, you just assume the absence of a value
defaults to 0?), but I figured I would let you guys know just in case!

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