Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RabbitMQTrigger not working with on-premises RabbitMQ and Azure Function Hybrid Connection #196

Open
madev4cloud opened this issue Jun 2, 2022 · 1 comment

Comments

@madev4cloud
Copy link

madev4cloud commented Jun 2, 2022

Environment:
.net 6
RabbitMQ installed in my laptop.
Azure Function hosted in Basic App Service Plan.
Hybrid Connection set up in my laptop and connected.

Cases:
When [RabbitMQTrigger] is used nothing happen. Message stays in queue.
When [TimeTrigger] is used with RabbitMQ.Client.ConnectionFactory and consumer.Received even - it works. Messages pick up by Function.

But nice to have [RabbitMQTrigger] working.

@sercandagdas
Copy link

This issue could be due to using a Basic app service plan.

Official documentation mentions that "The RabbitMQ bindings are only fully supported on [Premium] and [Dedicated App Service] plans.".

We are currently using [RabbitMQTrigger] with an on-premise RabbitMQ service with a premium app service plan, and it's working as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants