-
Notifications
You must be signed in to change notification settings - Fork 55
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
Error: Pipelining of requests forbidden when getting metrics #154
Comments
Can you elaborate on this a little bit more ? Do you get the |
I don't gent anything, the current code reuse the same IModel for evrything, for getting the metrics, for consuming and for publishing. It should use one IModel / thread and even use 2 connections (one for publish, one for consumemer) |
Thanks for clarifying that. Aside from our current implementation of IScaleMonitor and GetMetricsAsync(), can I get more info on what your function actually does as well, including the signature, etc ? This will help me narrow down on a plausible solution and also run some scenarios on our end. |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. |
I'm using 2 trigger function, one of them with a dead letter queue |
Hello,
When a function is running at the same time as the metric collector I get this exception:
Pipelining of requests forbidden
of type
System.NotSupportedException at RabbitMQ.Client.Impl.RpcContinuationQueue.Enqueue
The problem is that the same channel is used in different thread, this is not supported by RabbitMQ librar. Iit should use another
IModel
to do that.azure-functions-rabbitmq-extension/src/Trigger/RabbitMQListener.cs
Lines 187 to 197 in 09c079a
The text was updated successfully, but these errors were encountered: