RabbitMQ HTTP API for federation (add policy, add federation upstream) - no response

370 views
Skip to first unread message

Puiu Dan

unread,
Nov 2, 2016, 7:50:44 AM11/2/16
to rabbitmq-users
Hello

I am using an instance of rabbitmq running on my computer. I have installed the federation plugin.

I am using the HTTP API to register a new federation policy using the following request details:

PUT: http://localhost:15672/api/policies/%2f/myfederation
Content-Type: application/json
Body: {"pattern": "^amq\.", "definition": {"federation-upstream-set":"all"}, "priority": 1, "apply-to": "exchanges"}

The federation policy is registered in the broker (when I check it using the management interface) but I never receive any HTTP response. After time out I receive a no content message.

Do you have any ideas how to solve this issue? Or is there any problem in the way I created the request?

Thanks,
Dan

Michael Klishin

unread,
Nov 2, 2016, 8:00:28 AM11/2/16
to rabbitm...@googlegroups.com
What version is used? What's in server logs? Do you have e.g. a shell script that can reproduce
this with a couple of nodes with `curl`, for example?

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
MK

Staff Software Engineer, Pivotal/RabbitMQ

Puiu Dan

unread,
Nov 2, 2016, 9:04:06 AM11/2/16
to rabbitmq-users

Here we go:


RabbitMQ 3.6.1, Erlang 18.3


This are the requests. As you can see the get for status delivers the response. But the request for adding the policy not.



But even if the response was not delivered the policy was added:



RABBIT~1.LOG
Auto Generated Inline Image 1
Auto Generated Inline Image 2

Puiu Dan

unread,
Nov 2, 2016, 9:25:44 AM11/2/16
to rabbitmq-users
The problem might be on our side. The service is responding with an 204 status code. And our .net client and mozila REST client API do not interpret correctly the header. We will investigate in our side now:





On Wednesday, November 2, 2016 at 1:50:44 PM UTC+2, Puiu Dan wrote:
Auto Generated Inline Image 1
Reply all
Reply to author
Forward
0 new messages