[rabbitmq-discuss] shovel status improperly displayed on web UI

[Fred Dushin]

For my application intermittently stopping the shovel is a requirement in some cases (until we implement scheduled shovels); e.g, reconfiguration, bandwidth priority over a WAN, etc.

I have seen the same internal server error (3.0.1), but the problem goes away with a shovel restart, and we are not using the management console, except for debugging.

I'd like to start making suggestions about more CRUD management operations on shovels through the management APIs, but I need to study the mochiweb stuff in more detail.  Has this been discussed before?

-Fred

On Jan 21, 2013, at 5:45 AM, Simon MacMullen <simon at rabbitmq.com> wrote:

> On 20/01/13 16:40, mabra wrote:
>> Hello !
>> 
>> I am playing around with shovel and I am usually using the RabbitMQ Web
>> Management.
>> If I stop shovel via commandline, the status on the webpage causes an
>> "internal server error".
> 
> Good point - that's a bug. (Sort of - we normally assume you won't stop individual plugins by hand.)
> 
> Cheers, Simon
> 
> -- 
> Simon MacMullen
> RabbitMQ, VMware
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss