[rabbitmq-discuss] API aliveness test

Jason J. W. Williams jasonjwwilliams at gmail.com
Thu Aug 11 21:43:04 BST 2011


The documentation for the API aliveness-test call
(/api/aliveness-test/<vhost>) defines the success result
({"status":"ok"}), but not the failure results. When I use
"rabbitmqctl stop_app" to simulate a failure, I get fairly ugly
traceback returned over HTTP (https://gist.github.com/1140707) that'll
crash the JSON parser. So should I just do a string match for
{"status": "ok"} (or HTTP error code match) and consider any other
return a failure, or are there JSON-friendly error outputs as well?

Thank you in advance.


More information about the rabbitmq-discuss mailing list