Avoid assertQueues - connect without knowing the config of existing queue
See original GitHub issueSorry 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:
- Created 2 years ago
- Comments:6 (4 by maintainers)
Top GitHub Comments
You can reference it from your configuration file as described here, then depending on your IDE you should get basic auto complete
Understood. The schema might help.