question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Avoid assertQueues - connect without knowing the config of existing queue

See original GitHub issue

Sorry if i misunderstand the concept but i prefer my Clients not to need to create a queue but instead only use a single existing, permanent queue. Also my clients are not expected to know the exact configuration of the permanent queue, i cannot imagine maintaining a config file locally on tens of clients that reflects the current configuration of the central queue. Currently, without knowledge of the exact configuration of the central queue, clients cannot connect due to the use of assertQueue in Rascal.

For that, one must avoid the assertqueue function but instead only use checkQueue from amqplilb. It seems that rascal does not support this mode of operation. So i removed tasks.assertQueues, from Vhost.js here:

const init = async.compose(tasks.closeChannel, tasks.applyBindings, tasks.purgeQueues, tasks.checkQueues, tasks.assertQueues, tasks.checkExchanges, tasks.assertExchanges, tasks.createChannel, tasks.createConnection, tasks.checkVhost, tasks.assertVhost); Besides obviously removing the ability of the client to create a non existing queue on connect, would you expect any other issues like would rascal not try to reconnect forever when the rabbit host is down or such?

Thanks for the great library btw, just what i needed 😄

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:6 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
cressie176commented, Feb 17, 2022

You can reference it from your configuration file as described here, then depending on your IDE you should get basic auto complete

1reaction
cressie176commented, Feb 17, 2022

Understood. The schema might help.

Read more comments on GitHub >

github_iconTop Results From Across the Web

what is the difference between assertQueue and send To ...
assertQueue is an declaration of queue and sendToQueue is pushing your message in the queue. To be noted : Declaring a ...
Read more >
amqplib | Channel API reference - GitHub Pages
This will bork the channel if the named queue doesn't exist; if it does exist, you go through to the next round! There's...
Read more >
RabbitMQ tutorial - Work Queues
The main idea behind Work Queues (aka: Task Queues) is to avoid doing a resource-intensive task immediately and having to wait for it...
Read more >
jwalton/node-amqp-connection-manager - GitHub
assertQueue ('rxQueueName', { durable: true }); }, }); // Send some messages to the queue. If we're not currently connected, these will be...
Read more >
Mocking - Laravel - The PHP Framework For Web Artisans
This allows you to only test the controller's HTTP response without ... use the Bus facade's fake method to prevent jobs from being...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found