I would recommend amqp.node and bramqp over node-amqp. node-amqp has a lot of bugs and is poorly maintained, and it hides the “channel” concept which introduces a lot of problems for rabbitmq servers (because they are never closed).
Short answer: To requeue specific message you can pick both basic.reject or basic.nack with multiple flag set to false. basic.consume calling may also results to messages redelivering if you are using message acknowledge and there are un-acknowledged message on consumer at specific time and consumer exit without ack-ing them. basic.recover will redeliver all un-acked messages … Read more
Is true that on Celery there is a bit of confusion when you go to Queues, one thing you must keep in mind is that queue parameter refers to a Celery Kombu Queue Object and not directly to a AMQP queue, you can understand this by reading this extract from the docs. Of course the … Read more
@MSalters Re ‘message queue’: RabbitMQ’s default operation is exactly what you describe: transient pubsub. But with TCP instead of UDP. If you want guaranteed eventual delivery and other persistence and recovery features, then you CAN have that too – it’s an option. That’s the whole point of RabbitMQ and AMQP — you can have lots … Read more
There does not seem to be a direct AMQP-way to manage the server but there is a way you can do it from Python. I would recommend using a subprocess module combined with the rabbitmqctl command to check the status of the queues. I am assuming that you are running this on Linux. From a … Read more
Usually I use very simple approach to memorize something. I will provide all details below, but here is a simple picture of BasicProperties field and values. I’ve also tried to properly highlight queue/server and application context. If you want me to enhance it a bit – just drop a small comment. What I really want … Read more
Queue browsing is not supported directly, but if you declare a queue with NO auto acknowledgements and do not ACK the messages that you receive, then you can see everything in it. After you have had a look, send a CANCEL on the channel, or disconnect and reconnect to cause all the messages to be … Read more
I’m confused by your choice of three terms to compare. Within RabbitMQ, Fanout and Direct are exchange types. Pub-Sub is a generic messaging pattern but not an exchange type. And you didn’t even mention the 3rd and most important Exchange type, namely Topic. In fact, you can implement Fanout behavior on a Topic exchange just … Read more
I generally find it is best to have exchanges grouped by object type / exchange type combinations. in you example of user events, you could do a number of different things depending on what your system needs. in one scenario, it might make sense to have an exchange per event as you’ve listed. you could … Read more
RabbitMQ is an AMQP broker, while ActiveMQ is a JMS one. I suggest you read the AMQP wikipedia article to get an idea of the concepts used in AMQP, which are different than the ones you’re familiar in JMS. One of the main difference is that in AMQP a producer sends to an exchange without … Read more