Skip Menu |

This queue is for tickets about the Message-Passing-AMQP CPAN distribution.

Report information
The Basics
Id: 92939
Status: open
Priority: 0/
Queue: Message-Passing-AMQP
People
Owner: Nobody in particular
Requestors: DLAMBLEY [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: Normal
Broken in: 0.003
Fixed in: (no value)

History Show all quoted text
  Tue Feb 11 07:58:15 2014 DLAMBLEY [...] cpan.org - Ticket created
Subject: Reconnect fails for anonymous queues
If you're reading from an anonymous queue with Message::Passing::Input::AMQP, and the connection gets interrupted (for example by your broker restarting), it fails to reconnect. You can reproduce the error with this command line and restarting RabbitMQ, message-pass --output STDOUT --decoder JSON --encoder Null --input AMQP --input_options '{"exchange_name":"firehose","hostname":"127.0.0.1","username":"foo","password":"bar","queue_durable":0}'
  Wed Apr 01 10:50:32 2015 abraxxa [...] cpan.org - Correspondence added
Am Di 11. Feb 2014, 07:58:15, DLAMBLEY schrieb: Show quoted text
> If you're reading from an anonymous queue with > Message::Passing::Input::AMQP, and the connection gets interrupted > (for example by your broker restarting), it fails to reconnect. > > You can reproduce the error with this command line and restarting > RabbitMQ, > > message-pass --output STDOUT --decoder JSON --encoder Null --input > AMQP --input_options > '{"exchange_name":"firehose","hostname":"127.0.0.1","username":"foo","password":"bar","queue_durable":0}'
Dying because of a server restart is fixed by AnyEvent::RabbitMQ 1.15 which is the new required minimum version as of now, see RT#87705). I've tried your example and what happens instead is this instead: Failed to get queue at /home/ahartmai/perl5/perlbrew/perls/20/lib/site_perl/5.20.2/Message/Passing/AMQP/Role/DeclaresQueue.pm line 50. Patches welcome!
  Wed Apr 01 10:50:33 2015 The RT System itself - Status changed from 'new' to 'open'
  Sun Dec 13 15:38:52 2015 CAKIRKE [...] cpan.org - Correspondence added
On Wed Apr 01 10:50:32 2015, ABRAXXA wrote: Show quoted text
> Am Di 11. Feb 2014, 07:58:15, DLAMBLEY schrieb:
> > If you're reading from an anonymous queue with > > Message::Passing::Input::AMQP, and the connection gets interrupted > > (for example by your broker restarting), it fails to reconnect. > > > > You can reproduce the error with this command line and restarting > > RabbitMQ, > > > > message-pass --output STDOUT --decoder JSON --encoder Null --input > > AMQP --input_options > > '{"exchange_name":"firehose","hostname":"127.0.0.1","username":"foo","password":"bar","queue_durable":0}'
> > > Dying because of a server restart is fixed by AnyEvent::RabbitMQ 1.15 > which is the new required minimum version as of now, see RT#87705). > > I've tried your example and what happens instead is this instead: > Failed to get queue at > /home/ahartmai/perl5/perlbrew/perls/20/lib/site_perl/5.20.2/Message/Passing/AMQP/Role/DeclaresQueue.pm > line 50. > > Patches welcome!
testing with RabbitMQ shows this is expected behavior - server-generated queue names are restricted access by default. proposed PR https://github.com/suretec/Message-Passing-AMQP/pull/4 testable via: message-pass --output STDOUT --decoder JSON --encoder Null --input AMQP --input_options '{"exchange_name":"firehose","hostname":"127.0.0.1","username":"guest","password":"guest","queue_forget":1}'