Skip to main content

RabbitMQ synchronously consume messages

In my previous post I had described a scenario to synchronously consuming message from RabbitMQ. Here is a way to do it in python.To make things simple to understand I just wrote a dummy program that dumps the content of a RabbitMQ queue and then you can use the same program to remove a message also from queue by iterating all messages and acknowledging it. (its a dumb implementation so dont judge the coding, the intent is to demonstrate synchronous consumption of queue contents).



import sys
from amqplib import client_0_8 as amqp
messageIdToRemove = None
chan = None

def process_message(msg):
    print "================================================="
    print "Properties ="
    print msg.properties
    print "Body=" 
    print msg.body
    if op == "remove_message":
        if messageIdToRemove == msg.properties['message_id']:
            print "@@@@@@removing message@@@@@@@@@@@@@@@@@@"
            chan.basic_ack(msg.delivery_tag)
if __name__ == '__main__':
    if len(sys.argv) < 9:
       print "Usage python list_queue_messages.py mq_url mq_user mq_pass mq_vhost mq_exchange mq_queue_name mq_routing_key [list_queue|remove_message] messageIdToRemove"
       exit()
   
    mq_url = sys.argv[1]
    mq_user = sys.argv[2]
    mq_pass = sys.argv[3]
    mq_vhost = sys.argv[4]
    mq_exchange = sys.argv[5]
    mq_queue_name = sys.argv[6]
    mq_routing_key = sys.argv[7]
    op=sys.argv[8]
    if op == "remove_message":
        messageIdToRemove=sys.argv[9]
        
    conn = amqp.Connection(host=mq_url,
                           userid=mq_user,
                           password=mq_pass,
                           virtual_host=mq_vhost,
                           insist=False);
    chan = conn.channel();
    chan.queue_declare(queue=mq_queue_name, durable=True,
        exclusive=False, auto_delete=False);
    chan.exchange_declare(exchange=mq_exchange, type="direct", durable=True,
        auto_delete=False);        
    chan.queue_bind(queue=mq_queue_name, exchange=mq_exchange,
        routing_key=mq_routing_key)

    print "Consumer dumping messages from %s" % mq_queue_name
    i=0
    try:
        while True:
            msg = chan.basic_get(mq_queue_name)
            if msg is None:
                break;
            else:
                i=i+1
                process_message(msg)            
    finally:
        chan.close();
        conn.close();
    print "There are %d messages in the queue" % i

Comments

Popular posts from this blog

RabbitMQ java clients for beginners

Here is a sample of a consumer and producer example for RabbitMQ. The steps are Download Erlang Download Rabbit MQ Server Download Rabbit MQ Java client jars Compile and run the below two class and you are done. This sample create a Durable Exchange, Queue and a Message. You will have to start the consumer first before you start the for the first time. For more information on AMQP, Exchanges, Queues, read this excellent tutorial http://blogs.digitar.com/jjww/2009/01/rabbits-and-warrens/ +++++++++++++++++RabbitMQProducer.java+++++++++++++++++++++++++++ import com.rabbitmq.client.Connection; import com.rabbitmq.client.Channel; import com.rabbitmq.client.*; public class RabbitMQProducer { public static void main(String []args) throws Exception { ConnectionFactory factory = new ConnectionFactory(); factory.setUsername("guest"); factory.setPassword("guest"); factory.setVirtualHost("/"); factory.setHost("127.0.0.1"); factory.se...

Spring 3.2 quartz 2.1 Jobs added with no trigger must be durable.

I am trying to enable HA on nodes and in that process I found that in a two test node setup a job that has a frequency of 10 sec was running into deadlock. So I tried upgrading from Quartz 1.8 to 2.1 by following the migration guide but I ran into an exception that says "Jobs added with no trigger must be durable.". After looking into spring and Quartz code I figured out that now Quartz is more strict and earlier the scheduler.addJob had a replace parameter which if passed to true would skip the durable check, in latest quartz this is fixed but spring hasnt caught up to this. So what do you do, well I jsut inherited the factory and set durability to true and use that public class DurableJobDetailFactoryBean extends JobDetailFactoryBean {     public DurableJobDetailFactoryBean() {         setDurability(true);     } } and used this instead of JobDetailFactoryBean in the spring bean definition     <bean i...

Killing a particular Tomcat thread

Update: This JSP does not work on a thread that is inside some native code.  On many occasions I had a thread stuck in JNI code and it wont work. Also in some cases thread.stop can cause jvm to hang. According to javadocs " This method is inherently unsafe. Stopping a thread with Thread.stop causes it to unlock all of the monitors that it has locked". I have used it only in some rare occasions where I wanted to avoid a system shutdown and in some cases we ended up doing system shutdown as jvm was hung so I had a 70-80% success with it.   -------------------------------------------------------------------------------------------------------------------------- We had an interesting requirement. A tomcat thread that was spawned from an ExecutorService ThreadPool had gone Rogue and was causing lots of disk churning issues. We cant bring down the production server as that would involve downtime. Killing this thread was harmless but how to kill i...