aliveness-test is missing from version rabbitmq 3.4.1 Erlang R16B03

[MichalKM]

Hey

Does someone know where it moved ?

http://<hostname>:15672/api/aliveness-test/%2F

Thanks

This e-mail, as well as any attached document, may contain material which is confidential and privileged and may include trademark, copyright and other intellectual property rights that are proprietary to Kenshoo Ltd,  its subsidiaries or affiliates ("Kenshoo"). This e-mail and its attachments may be read, copied and used only by the addressee for the purpose(s) for which it was disclosed herein. If you have received it in error, please destroy the message and any attachment, and contact us immediately. If you are not the intended recipient, be aware that any review, reliance, disclosure, copying, distribution or use of the contents of this message without Kenshoo's express permission is strictly prohibited.

[Michael Klishin]

On 25 January 2015 at 11:38:51, MichalKM (michal.kel...@kenshoo.com) wrote:
> Does someone know where it moved ?
>

> http://:15672/api/aliveness-test/%2F

It didn't move anywhere. With 3.4.3:

$ curl -u guest:guest http://127.0.0.1:15672/api/aliveness-test/%2F
{"status":"ok"}

Perhaps you are providing an incorrect vhost name. For example, with a non-existent vhost, I get

$ curl -u guest:guest http://127.0.0.1:15672/api/aliveness-test/aaaaa
{"error":"Object Not Found","reason":"\"Not Found\"\n"} 
--
MK

Staff Software Engineer, Pivotal/RabbitMQ

[Michal Kelner-Mishali]

It was actually a problem with the queue itself, marked as durable=true.

Once I removed it, it was recreated as durable=false and I was able to recreate it over and over again.

The error was missleading, it gave me error 406, as a regular user and 400 as admin.

Thanks

--

Michal Kelner Mishali
Monitoring Technical Developer // Kenshoo
Office +972 73 2862 *445 // Mobile +972 54 322-8525

Infinite Optimization™ powered by Infinite Innovation
Kenshoo.com/Israel

[Michael Klishin]

 On 25 January 2015 at 21:26:09, Michal Kelner-Mishali (michal.kel...@kenshoo.com) wrote:
> It was actually a problem with the queue itself, marked as durable=true.
> Once I removed it, it was recreated as durable=false and I was
> able to recreate it over and over again.
> The error was missleading, it gave me error 406, as a regular user
> and 400 as admin.

It should be 406 for every user but when you delete and re-create something multiple times
you may hit another issue. "Parameters do not match the original declaration" always results in a 406 channel error.