Closed danielscholl closed 5 years ago
anthonyvercolano
commented
5 years ago @danielscholl thank you for the issue.
We'll be looking at this right away. Will be examining the flow control state to see where things are going wrong.
The messages are clearly being queued in the iot amqp transport. The only reason they aren't going out on the wire would be if the amqp transport RHEA is indicating that it is not in a sendable state. Don't think that this is a RHEA problem though.
danielscholl
commented
5 years ago @anthonyvercolano this issue is resolved in release 1.11.0.
├─┬ azure-iot-device@1.11.0 │ ├─┬ azure-iot-common@1.10.1 │ │ ├── debug@4.1.1 deduped │ │ └─┬ getos@3.1.1 │ │ └─┬ async@2.6.1 │ │ └── lodash@4.17.15 deduped │ ├─┬ azure-iot-http-base@1.9.10 │ │ ├── azure-iot-common@1.10.1 deduped │ │ ├── debug@4.1.1 deduped │ │ └── uuid@3.3.3 deduped │ ├─┬ azure-storage@2.10.3 │ │ ├── browserify-mime@1.2.9 │ │ ├── extend@3.0.2 │ │ ├─┬ json-edm-parser@0.1.2 │ │ │ └── jsonparse@1.2.0 │ │ ├─┬ md5.js@1.3.4 │ │ │ ├─┬ hash-base@3.0.4 │ │ │ │ ├── inherits@2.0.4 deduped │ │ │ │ └── safe-buffer@5.2.0 deduped │ │ │ └── inherits@2.0.4 │ │ ├─┬ readable-stream@2.0.6 │ │ │ ├── core-util-is@1.0.2 │ │ │ ├── inherits@2.0.4 deduped │ │ │ ├── isarray@1.0.0 │ │ │ ├── process-nextick-args@1.0.7 │ │ │ ├── string_decoder@0.10.31 │ │ │ └── util-deprecate@1.0.2 │ │ ├─┬ request@2.88.0 │ │ │ ├── aws-sign2@0.7.0 │ │ │ ├── aws4@1.8.0 │ │ │ ├── caseless@0.12.0 │ │ │ ├─┬ combined-stream@1.0.8 │ │ │ │ └── delayed-stream@1.0.0 │ │ │ ├── extend@3.0.2 deduped │ │ │ ├── forever-agent@0.6.1 │ │ │ ├─┬ form-data@2.3.3 │ │ │ │ ├── asynckit@0.4.0 │ │ │ │ ├── combined-stream@1.0.8 deduped │ │ │ │ └── mime-types@2.1.24 deduped │ │ │ ├─┬ har-validator@5.1.3 │ │ │ │ ├─┬ ajv@6.10.2 │ │ │ │ │ ├── fast-deep-equal@2.0.1 │ │ │ │ │ ├── fast-json-stable-stringify@2.0.0 │ │ │ │ │ ├── json-schema-traverse@0.4.1 │ │ │ │ │ └─┬ uri-js@4.2.2 │ │ │ │ │ └── punycode@2.1.1 │ │ │ │ └── har-schema@2.0.0 │ │ │ ├─┬ http-signature@1.2.0 │ │ │ │ ├── assert-plus@1.0.0 │ │ │ │ ├─┬ jsprim@1.4.1 │ │ │ │ │ ├── assert-plus@1.0.0 deduped │ │ │ │ │ ├── extsprintf@1.3.0 │ │ │ │ │ ├── json-schema@0.2.3 │ │ │ │ │ └─┬ verror@1.10.0 │ │ │ │ │ ├── assert-plus@1.0.0 deduped │ │ │ │ │ ├── core-util-is@1.0.2 deduped │ │ │ │ │ └── extsprintf@1.3.0 deduped │ │ │ │ └─┬ sshpk@1.16.1 │ │ │ │ ├─┬ asn1@0.2.4 │ │ │ │ │ └── safer-buffer@2.1.2 deduped │ │ │ │ ├── assert-plus@1.0.0 deduped │ │ │ │ ├─┬ bcrypt-pbkdf@1.0.2 │ │ │ │ │ └── tweetnacl@0.14.5 deduped │ │ │ │ ├─┬ dashdash@1.14.1 │ │ │ │ │ └── assert-plus@1.0.0 deduped │ │ │ │ ├─┬ ecc-jsbn@0.1.2 │ │ │ │ │ ├── jsbn@0.1.1 deduped │ │ │ │ │ └── safer-buffer@2.1.2 deduped │ │ │ │ ├─┬ getpass@0.1.7 │ │ │ │ │ └── assert-plus@1.0.0 deduped │ │ │ │ ├── jsbn@0.1.1 │ │ │ │ ├── safer-buffer@2.1.2 │ │ │ │ └── tweetnacl@0.14.5 │ │ │ ├── is-typedarray@1.0.0 │ │ │ ├── isstream@0.1.2 │ │ │ ├── json-stringify-safe@5.0.1 │ │ │ ├─┬ mime-types@2.1.24 │ │ │ │ └── mime-db@1.40.0 │ │ │ ├── oauth-sign@0.9.0 │ │ │ ├── performance-now@2.1.0 │ │ │ ├── qs@6.5.2 │ │ │ ├── safe-buffer@5.2.0 │ │ │ ├─┬ tough-cookie@2.4.3 │ │ │ │ ├── psl@1.3.0 │ │ │ │ └── punycode@1.4.1 │ │ │ ├─┬ tunnel-agent@0.6.0 │ │ │ │ └── safe-buffer@5.2.0 deduped │ │ │ └── uuid@3.3.3 deduped │ │ ├── underscore@1.8.3 │ │ ├── uuid@3.3.3 deduped │ │ ├── validator@9.4.1 │ │ ├─┬ xml2js@0.2.8 │ │ │ └── sax@0.5.8 │ │ └── xmlbuilder@9.0.7 │ ├─┬ debug@4.1.1 │ │ └── ms@2.1.2 │ ├── lodash@4.17.15 │ ├─┬ machina@4.0.2 │ │ └── lodash@4.17.15 deduped │ └── traverse@0.6.6 └─┬ azure-iot-device-amqp@1.10.1 ├─┬ async@2.6.3 │ └── lodash@4.17.15 deduped ├─┬ azure-iot-amqp-base@2.2.11 │ ├─┬ async@2.6.3 │ │ └── lodash@4.17.15 deduped │ ├── azure-iot-common@1.10.1 deduped │ ├── debug@4.1.1 deduped │ ├── lodash.merge@4.6.2 │ ├── machina@4.0.2 deduped │ ├── rhea@1.0.8 deduped │ ├── uuid@3.3.3 deduped │ └─┬ ws@6.2.1 │ └── async-limiter@1.0.1 ├── azure-iot-common@1.10.1 deduped ├── azure-iot-device@1.11.0 deduped ├── debug@4.1.1 deduped ├── machina@4.0.2 deduped ├─┬ rhea@1.0.8 │ └─┬ debug@3.2.6 │ └── ms@2.1.2 deduped └── uuid@3.3.3
pierreca
commented
5 years ago That's great to hear :) closing the issue. Thanks!
az-iot-builder-01
commented
5 years ago @danielscholl, thank you for your contribution to our open-sourced project! Please help us improve by filling out this 2-minute customer satisfaction survey
Context
OS and version used: Ubuntu 18.04.01 LTS (bionic)
Node.js version: iotedge 1.0.6.1 (3fa6cbef8b7fc3c55a49a622735eb1021b8a5963)
npm version: 6.9.0
list of installed packages:
Description of the issue:
Using the nodejs SDK to send device to cloud messages with the AMQP protocol to an iotedge. The messages are sent successfully at 1 second intervals until 2047 and then messages actually stop being sent with no error being thrown.
Code sample exhibiting the issue:
https://raw.githubusercontent.com/Azure/azure-iot-sdk-node/master/device/samples/edge_downstream_device.js
Console log of the issue: