AMQP error message

[tobilg]

When trying to implement topic-based routing with RabbitMQ and Tile38, I'm seeing the following error message:

Endpoint connect/send error: 48: amqp://guest:guest@127.0.0.1:5672/webhook-events?type=topic&route=hook.http: Exception (406) Reason: "PRECONDITION_FAILED - inequivalent arg 'type' for exchange 'webhook-events' in vhost '/': received 'direct' but current is 'topic'"

I'm pretty confident I set up the exchange correctly:

I don't understand where the received 'direct' but current is 'topic' is coming from unfortunately. Do you happen to have an idea? Thanks!

[tobilg]

Ok, so I deleted the exchange from RabbitMQ, deleted all hooks from Tile38 and created a new one with the amqp://guest:guest@127.0.0.1:5672/webhook-events?type=topic&route=hook.http endpoint.

Turns out Tile38 creates the queue and exchanges, but it seems to default to type direct, even if the connection string says type=topic.

I suspect the type parameter is not respected, as direct seems to be always set: https://github.com/tidwall/tile38/blob/master/controller/endpoint/amqp.go#L73 Also, the type param seems to be missing from https://github.com/tidwall/tile38/blob/master/controller/endpoint/endpoint.go#L54 and https://github.com/tidwall/tile38/blob/master/controller/endpoint/endpoint.go#L485 only seems to be able to set the route param.

[tidwall]

I'm seeing the same issue. From http://tile38.com/commands/sethook :

The following optional parameters are available for this 
hook, the listed value is the default value:

type - ‘direct’
durable - true
immediate - false
mandatory - false
auto_delete - false
internal - false
no_wait - false
delivery_mode - 1
route - tile38

But it seems that the only available option is route.
I could wire up all these options, but other than route and type, do we actually need them all to be customizable through the webhook uri?

[tobilg]

Thanks for the fast response! I think it’d be great to be able to set all these parameters via the endpoint query string, as outlined in the docs.

[tidwall]

Sounds good. I'll see what I can do. Thanks

[tidwall]

I just pushed an update that allows for setting each of the paramaters.

[tobilg]

Thanks a lot! Is the Docker image „latest“ tag built automatically?

I guess there will be another release soon as well? That’d be great 😀👍🏻

[tidwall]

It does build automatically, but it tracks the latest version, not the master branch.

In this case latest -> v1.12.0.

I may need to figure out a better approach. Is it normal for docker latest tag to track the master branch?

[tobilg]

I’d say it is a common practice to have latest point to master. Other people might disagree though... 😀

[tobilg]

@tidwall is this change in the current latest Docker image? The exchange seems still to be set to direct even when specifying topic in the endpoint URI... I'm asking because https://hub.docker.com/r/tile38/tile38/tags/ shows that latest was built 2 days ago. Thanks!