Resolved! The problem was caused for this call:
session = connection.session(str(uuid4())) This is in all python examples! Parent and children processes got the same session id because uuid4() was returning the same uuid for both processes. I merged the PID with "str(uuid4())", to get different sessions id, and everything worked perfect. Shouldn't uuid4 return random unique values? Thanks for your help!! Joshua, thanks for graphic! It's very helpful!! -- Caio Brentano On Fri, Mar 26, 2010 at 2:18 PM, Joshua Kramer <[email protected]>wrote: > > I think from the snippet of code you sent, you have a good understanding > how everything works with regards to local and server queues. I've attached > the graphic that was in the article (they put the wrong graphic in the > magazine article) that explains how you might have more than one consumer on > a queue. The code included with my article definitely demonstrates this. > I'll watch the mail list to see if you have any further questions. :) > > On Fri, 26 Mar 2010, Caio Brentano wrote: > > Date: Fri, 26 Mar 2010 12:02:32 -0300 >> From: Caio Brentano <[email protected]> >> Reply-To: [email protected] >> To: Joshua Kramer <[email protected]> >> Cc: [email protected] >> Subject: Re: Multiprocess Python Client >> >> >> Joshua, thanks for the Article... I'll read it carefully! =) >> >> Answering to Alan: It is the C++ Broker! >> >> About the code, what I tried to is very simple, I just want parent and >> child >> process reading the same queue... >> >> ========================================================================= >> def consume_queues(server_queue_name): >> >> session = connect_to_broker() >> >> my_pid = str(os.getpid()) >> local_queue_name = 'local_' + my_pid + server_queue_name >> >> queue = session.incoming(local_queue_name) >> session.message_subscribe(queue=server_queue_name, >> destination=local_queue_name) >> queue.start() >> >> dump_queue(session, local_queue) >> >> if __name__ == "__main__": >> >> queue_name = "queue_for_test" >> >> try: >> pid = os.fork() >> if pid == 0: >> # Child start to consume queues >> consume_queues(queue_name) >> os._exit(0) >> else: >> consume_queues(queue_name) >> child_pid = os.wait() >> print 'process ' + str(child_pid) + 'has finished' >> sys.exit(0) >> except OSError, error: >> print 'Unable to fork. Error: %d (%s)' % (error.errno, >> error.strerror) >> sys.exit(-1) >> ========================================================================= >> >> Function *dump_queue* is similar to pubsub topic publisher example. >> >> >> >> >> On Fri, Mar 26, 2010 at 1:18 PM, Joshua Kramer <[email protected] >> >wrote: >> >> >>> Is there anyway to do a multiprocess client to consume a queue? >>> >>>> >>>>> >>>> Hello Caio, >>> >>> I wrote a Linux Journal article last year illustrating this exact >>> concept. >>> You can find it here: >>> >>> >>> http://www.linuxjournal.com/magazine/advanced-message-queuing-protocol-amqp >>> >>> If you'd like a copy of the graphic (they seem to have broken it) let me >>> know. >>> >>> Thanks, >>> -Josh >>> >>> -- >>> >>> ----- >>> http://www.globalherald.net/jb01 >>> GlobalHerald.NET, the Smarter Social Network! (tm) >>> >>> >> >> >> >> > -- > > ----- > http://www.globalherald.net/jb01 > GlobalHerald.NET, the Smarter Social Network! (tm) > -- Caio Brentano
