[rabbitmq-discuss] Login woes with the Ruby amqp library
meyer at paperplanes.de
Tue Jul 21 20:32:22 BST 2009
I'm trying to hunt down a problem that I can reproduce with the Ruby
amqp library by Aman, and RabbitMQ 1.6. I'm not sure on which end of
both the actual problem is, maybe you have some ideas.
The problem is rather simple, I try to log in with invalid data.
RabbitMQ's way seems to be to log an error and shutdown the
connection. The library on the other hand doesn't seem to take that
too seriously, and tries reopening connections like crazy, immediately
after the previous connection has been closed. Obviously the log is
showing the right errors with access_refused as you'd expect, but I'm
not sure if that error actually reaches the client or is handled by it
in any way. Does the server return the error to the client at all?
That'd probably mean the problem is on the library's end. I tried the
whole thing with bunny, and it at least realizes there's no more data
coming from the server, but obviously it uses a more procedural
approach compared to the EventMachine-based amqp library.
Any pointers would be most welcome. The problem I end up with with
these endless reconnect is an Erlang VM that eats up CPU like crazy,
and that's not great.
http://paperplanes.de | http://holgarific.net
More information about the rabbitmq-discuss