Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

406 (PRECONDITION-FAILED) error leads to too many connection attempts #77

Closed
azzang opened this issue Mar 29, 2019 · 1 comment
Closed
Labels

Comments

@azzang
Copy link

azzang commented Mar 29, 2019

When a 406 is triggered, I'd expect to see an attempt at reestablishing a connection in reconnectTimeInSeconds seconds, but I'm seeing them happen more frequently.

One way to reproduce:

  1. clone the repository / npm install
  2. run receiver.js (in examples)
  3. in sender.js, edit the line that asserts the queue by setting durable to false (i.e. set up a 406)
  4. in a new terminal, run sender.js

Note how fast connection attempts are happening.

azzang pushed a commit to azzang/node-amqp-connection-manager that referenced this issue Apr 1, 2019
azzang pushed a commit to azzang/node-amqp-connection-manager that referenced this issue Apr 1, 2019
benbriadeploy pushed a commit that referenced this issue Apr 1, 2019
## [2.3.1](v2.3.0...v2.3.1) (2019-04-01)

### Bug Fixes

* prevent too many connection attempts on error ([2760ce5](2760ce5)), closes [#77](#77)
@benbriadeploy
Copy link

🎉 This issue has been resolved in version 2.3.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants