[rabbitmq-discuss] list_connections failing

Mon Nov 9 20:08:05 GMT 2009

Hi Tim,

I did reply to your question about Bunny on GitHub. I asked if you  
could show me some code so that I can try to help. I'm not sure what  
you are trying to do that is causing a problem, therefore it's very  
difficult to come up with sensible suggestions. Although I have  
forgotten to update the Bunny Readme to say that it can be used with  
RabbitMQ 1.7.0, I use it with 1.7.0 all the time.

Regards,

Chris

On 9 Nov 2009, at 16:15, Tim Rosenblatt wrote:

> Thanks for the fast response, David.
>
> I don't think upgrading is possible right now. We've got a deadline  
> to show this project in the next few weeks, and I'm using the Bunny  
> gem in Ruby, which isn't yet compatible with 1.7.0. Changing  
> versions of Rabbit as well as changing the library being feels  
> unwise at this point.
>
> For the future, in case Bunny isn't upgraded, do you have a  
> recommended library for Ruby? I need the ability to publish to  
> named queues, and subscribe to them.
>
> You say that it sounds like the "prevent timeouts when server is  
> busy". What defines "busy" here? Is that when the server is in the  
> middle of something at the moment I run the command, and if I just  
> run it a few more times, I'll eventually get through? Or is there  
> something deeper here?
>
> Thanks.
>
> On Mon, Nov 9, 2009 at 10:54 AM, David Wragg  
> <david.wragg at lshift.net> wrote:
> Hi Tim,
>
> Tim Rosenblatt <tim at cloudspace.com> writes:
> > I'm running RabbitMQ 1.5.4 on Ubuntu, and when I run `rabbitmqctl
> > list_connections`, I usually get the following output
> >
> > [...]
> >
> > Obviously it looks like a timeout, but it comes back after only  
> ~5 seconds,
> > which seems very short for a timeout. Sometimes this does list the
> > connections -- there's only ever 10, which is the correct number  
> -- but it
> > often fails. This was working fine until a few days ago, when for  
> no obvious
> > reason, it started returning this. I am logged in as root when  
> running this.
>
> This sounds similar to an issue that was fixed in 1.7.0 ("prevent
> timeouts of rabbitmqctl when the server is busy").  Could you migrate
> to 1.7.0 and see if it solves your problem?
>
> (Note that migrating from 1.5.4 to 1.7.0 involves a database schema
> change - see the "Upgrading" section of the release notes at
> <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/ 
> 20091007/3aaed239/attachment.txt>)
>
> David
>
> --
>  [][][] David Wragg       | mail: david.wragg at lshift.net
>   [][] Senior Developer  | tel: +44 (0)20 7729 7060
>  []  [] LShift Ltd        | web: www.lshift.net
>
>
>
> -- 
> Tim Rosenblatt
> Cloudspace
> Office: 407-823-8808
> Cell: 407-719-2777
>
> 10244 E Colonial Dr, Suite 106
> Orlando, FL 32817
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20091109/230a1515/attachment.htm 