[rabbitmq-discuss] Problem when hitting /api/queues in rabbitmq management API
andrew at glyde.com
Tue Dec 21 19:15:29 GMT 2010
Sweet! That new .ez file you linked me to worked great.
I was seeing that "api/queues" error even when I didn't have any
consumers attached. However, I'm running the management plugin against
a rabbit in our dev environment where the server is a shared resource
for several developers. It is quite possible that at some point in
development we had an exclusive consumer subscribed to queue.
On Tue, Dec 21, 2010 at 3:45 AM, Simon MacMullen <simon at rabbitmq.com> wrote:
> On 21/12/10 00:46, andrew chase wrote:
>> I'm not sure whether I should be asking this question here, or if
>> there's a different path for communicating problems with the
>> rabbitmq-management plugin. I thought about opening an issue via
>> github, but it looks like the rabbitmq-managment committers are
>> already using mercurial for ticket tracking.
> Hi Andrew. The rabbitmq-management committers are the RabbitMQ committers,
> so here is the right place :)
>> I have been really impressed with the management plugin, however, I am
>> having problems with making GET requests to the "/apis/queues" route.
>> When requesting that path I get back a 500 Internal server error. In
>> the rabbitmq log file the error is being logged as:
>> =ERROR REPORT==== 20-Dec-2010::16:21:58 ===
>> webmachine error: path="/api/queues"
> Hmm. Looks like you found a bug. Are you using exclusive consumers by any
> Could you try replacing your rabbitmq-management-2.2.0.ez with
> and see if that fixes the problem?
>> Also, I'm running Erlang R13B01. Could that be the problem?
> No, R13B01 should be OK.
> Cheers, Simon
> Simon MacMullen
> Staff Engineer, RabbitMQ
> SpringSource, a division of VMware
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
More information about the rabbitmq-discuss