RabbitMQ 3.4.0 Management plugin. Queues page gives "ReferenceError: queue is not defined"

[Alex Shkop]

Hi, all

Just updated RabbitMQ server to 3.4.0. Now I can't access Queues page in management plugin. Instead of queue listing it states:

ReferenceError: queue is not defined

Also in JS console I see "Uncaught before/after mismatch". Not sure this errors are connected.

Browser cache cleared, repeatable in Chrome and FF.

Does anyone except me is affected by this issue?

Thanks

[Simon MacMullen]

I don't see it I'm afraid.

Are you able to see the same on a different server? With a different
client machine? Is there a proxy in the way?

Just casting around for ideas on what it might be.

Cheers, Simon

[Andrey Kuznetsov]

Has same issue.

List stops work when I has some 'autogenerated' queues, like 'amq.gen-61i9L7gV3UyZ8Ih_Ssk2-A'

We use them in RPC-style communications.

As long I close all RPC-clients and queues are removed -- list starts working again.

[an101]

I'm seeing exactly the same problem - tested with latest IE, Firefox and Chrome and all three show a ' ReferenceError: 'queue' is undefined' when accessing the queues page.  

Here's a pic:

[an101]

Simon,

I've finally been able to reproduce the issue consistently.  

If the server has NO (zero) connections, I'm able to see the list of queues.  I then trigger a connection to the server and the list of queues is not longer accessible through the management visualiser.  If I force close the connection, the list of queues is available again.  

Michael

[Andrey Kuznetsov]

Do you certain that it's the connection?

I have working Queues page with just a subscriber connection working with no issues.

And just as I call channel.QueueDeclare() ( http://www.rabbitmq.com/releases/rabbitmq-dotnet-client/v3.4.0/rabbitmq-dotnet-client-3.4.0-client-htmldoc/html/type-RabbitMQ.Client.IModel.html#method-M:RabbitMQ.Client.IModel.QueueDeclare ) page instantly breaks and "ReferenceError: queue is not defined" shows.

I'm breaking connection that created queue and reload queues page and it's working again.

[Alex Shkop]

I removed all my auto-named queue, but issue persists. So I think the problem is not in names but perhaps in some other attribute of queue.

Does your page work if there are some queues with assigned names?

пятница, 24 октября 2014 г., 6:15:50 UTC+3 пользователь Andrey Kuznetsov написал:

[Andrey Kuznetsov]

Yes

But it breaks at first queue like 

 (screenshot from 3.3.5 version)

[Simon MacMullen]

On 24/10/14 09:38, Andrey Kuznetsov wrote:
> But it breaks at first queue like
>

> <https://lh5.googleusercontent.com/-M5_ywxXAVWI/VEoP1K-Cj-I/AAAAAAAAA7U/mLR_y3CUq7A/s1600/Capture.PNG> (screenshot
> from 3.3.5 version)

Right, got it. It's a completely trivial bug in the web UI rendering for
exclusive queues which crept in at the last minute. How incredibly annoying.

You can work around it by clicking on "+/-" and disabling the "Features
(with policy)" and "Features (no policy)" columns.

But in order to do that you need to be able to see the queues table. If
you can't see it you can do one of:

1) temporarily create an empty vhost then add a queue to it.

2) open the JavaScript console and invoke this then refresh:

store_pref("column-queues-features", false);

A fix for this bug will be in tonight's nightly build, and will be in 3.4.1.

Cheers, Simon

[Andrey Kuznetsov]

Fix with JavaScript worked like a charm.

Thanks.