Management plugin, JSON encode error "bad term" x-cancel-on-ha-failover starting from v3.6.7 #1159
Comments
|
Sorry I had to push this in https://github.com/rabbitmq/rabbitmq-management/issues Maybe is a duplicate of rabbitmq/rabbitmq-management-agent#34? but I'm using erlang 19.0 and I also tested RabbitMQ v3.6.8 with same error If there's no consumer the queue is accessible. |
|
It's the same issue as rabbitmq/rabbitmq-management-agent#34 but in a different place. How can this be reproduced so that I can file a new issue there? |
|
OK, so looks like adding a consumer with extra arguments should be enough. |
I'm using EasyNetQ, just install the latest version from nuget, then this is the c# code: using System;
using EasyNetQ;
namespace BadTermIssue
{
public class Program
{
public static void Main(string[] args)
{
var bus = RabbitHutch.CreateBus("host=127.0.0.1", x => x.Register<IEasyNetQLogger>(s => new EasyNetQ.Loggers.ConsoleLogger()));
bus.Receive<MyMessage>("BAD_TERM_ISSUE", message => { });
Console.WriteLine("Press enter to stop the consumer and exit the application...");
Console.ReadLine();
bus.Dispose();
}
}
public class MyMessage
{
}
}When it's running try to access the queue -> http://localhost:15672/#/queues/%2F/BAD_TERM_ISSUE |
|
Moved to rabbitmq/rabbitmq-management-agent#39, we can reproduce. |
|
@micdenny rabbitmq/rabbitmq-management-agent#39 is fixed and will be in |
|
tested and it works like a charm |
When there's a consumer connected to a queue with
x-cancel-on-ha-failover, is not possible to open the queue detail from the management plugin.RabbitMQ 3.6.7
Erlang: 19.0
With RabbitMQ 3.6.6 it works with the same erlang version 19.0
Here's the error:
The text was updated successfully, but these errors were encountered: