The issue was unrelated. I tested this patch with both rabbit 1.8 and 2.6 and it seems to work so far. I'll give it some more testing and report if there are any weird issues.
David what do you think ? On 10/10/2011 06:51 PM, ext [email protected] wrote: > I wanted to try this but the BOSS daemon fails to complete the > connection to this recent amqp server. I'll debug and see if I can get > both ends to connect and work. > > On 10/10/2011 05:12 PM, ext Bartosh, Eduard wrote: >> This trivial patch fixes this issue for me: >> --- a/RuoteAMQP/participant.py >> +++ b/RuoteAMQP/participant.py >> @@ -78,11 +78,11 @@ class Participant(object): >> queue=self._queue, durable=True, exclusive=False, >> auto_delete=False) >> # Currently ruote-amqp uses the anonymous direct exchange >> - self._chan.exchange_declare( >> - exchange="", type="direct", durable=True, >> auto_delete=False) >> + #self._chan.exchange_declare( >> + # exchange="", type="direct", durable=True, >> auto_delete=False) >> # Bind our queue using a routing key of our queue name >> - self._chan.queue_bind( >> - queue=self._queue, exchange="", routing_key=self._queue) >> + #self._chan.queue_bind( >> + # queue=self._queue, exchange="", >> routing_key=self._queue) >> # and set a callback for workitems >> self._consumer_tag = self._chan.basic_consume( >> queue=self._queue, no_ack=False, >> >> The reason for the issue as far as I can see is the check >> check_not_default_exchange introduced in rabbitmq server code somewhere >> between versions 2.1.0 and 2.1.1. >> However, by default the default exchange is implicitly bound to every queue, >> with a routing key equal to the queue name. So, my patch just removes >> exchange declaration and queue binding as it's done by default. >> >> I'm not sure this default behaviour would work for older versions of >> rabbitmq server. Can anyone check if it works for rabbitmq 1.8? >> >> Thanks, >> Ed >> >>> -----Original Message----- >>> From: [email protected] [mailto:meego- >>> [email protected]] On Behalf Of Bartosh, >>> Eduard >>> Sent: Monday, October 10, 2011 1:57 PM >>> To: [email protected] >>> Subject: [Meego-distribution-tools] ruote-amqp-pyclient crashes when >>> declaring exchange >>> >>> Hi, >>> >>> Recently I've upgraded rabbitmq-server to 2.6.1 and as a result I see >>> this traceback when running my participant: >>> Traceback (most recent call last): >>> File "/usr/bin/boss-participant-gerrit", line 190, in <module> >>> sys.exit(main()) >>> File "/usr/bin/boss-participant-gerrit", line 185, in main >>> run_participant(config) >>> File "/usr/bin/boss-participant-gerrit", line 140, in run_participant >>> config.get('obs_webui')) >>> File "/usr/bin/boss-participant-gerrit", line 35, in __init__ >>> amqp_routing_key=amqp_settings['amqp_routing_key']) >>> File "/usr/lib/python2.7/site-packages/RuoteAMQP/participant.py", >>> line 53, in __init__ >>> auto_delete=False) >>> File "/usr/lib/python2.7/site- >>> packages/amqplib/client_0_8/channel.py", line 843, in exchange_declare >>> (40, 11), # Channel.exchange_declare_ok >>> File "/usr/lib/python2.7/site- >>> packages/amqplib/client_0_8/abstract_channel.py", line 105, in wait >>> return amqp_method(self, args) >>> File "/usr/lib/python2.7/site- >>> packages/amqplib/client_0_8/channel.py", line 273, in _close >>> (class_id, method_id)) >>> amqplib.client_0_8.exceptions.AMQPChannelException: (403, >>> u'ACCESS_REFUSED - operation not permitted on the default exchange', >>> (40, 10), 'Channel.exchange_declare') >>> >>> It worked just fine with rabbitmq 1.8.0. >>> >>> ruote-amqp-pyclient version is 1.12 >>> >>> Any idea how to fix this? >>> >>> >>> Thanks, >>> Ed >>> --------------------------------------------------------------------- >>> Intel Finland Oy >>> Registered Address: PL 281, 00181 Helsinki >>> Business Identity Code: 0357606 - 4 >>> Domiciled in Helsinki >>> >>> This e-mail and any attachments may contain confidential material for >>> the sole use of the intended recipient(s). Any review or distribution >>> by others is strictly prohibited. If you are not the intended >>> recipient, please contact the sender and delete all copies. >>> >>> _______________________________________________ >>> MeeGo-distribution-tools mailing list >>> [email protected] >>> http://lists.meego.com/listinfo/meego-distribution-tools >> --------------------------------------------------------------------- >> Intel Finland Oy >> Registered Address: PL 281, 00181 Helsinki >> Business Identity Code: 0357606 - 4 >> Domiciled in Helsinki >> >> This e-mail and any attachments may contain confidential material for >> the sole use of the intended recipient(s). Any review or distribution >> by others is strictly prohibited. If you are not the intended >> recipient, please contact the sender and delete all copies. >> >> _______________________________________________ >> MeeGo-distribution-tools mailing list >> [email protected] >> http://lists.meego.com/listinfo/meego-distribution-tools > > > > _______________________________________________ > MeeGo-distribution-tools mailing list > [email protected] > http://lists.meego.com/listinfo/meego-distribution-tools -- Thanks, Islam Amer
signature.asc
Description: OpenPGP digital signature
_______________________________________________ MeeGo-distribution-tools mailing list [email protected] http://lists.meego.com/listinfo/meego-distribution-tools
