azure-webjobs-sdk: `beta.5` Seems Very Broken with Queues
Please provide a succinct description of the issue.
Repro steps
Upgrading from beta.1 to beta.5, Queues stop working and appear to silently fail. Messages immediately get sent to point queue without any exception/warning/message provided.
Sample output:
Host.Startup: Information: Found the following functions:
Applications.Authentications.Host.Get
Host.Startup: Information: Job host started
Microsoft.Hosting.Lifetime: Information: Now listening on: https://localhost:...
Microsoft.Hosting.Lifetime: Information: Now listening on: http://localhost:...
Microsoft.Hosting.Lifetime: Information: Application started. Press Ctrl+C to shut down.
Microsoft.Hosting.Lifetime: Information: Hosting environment: Development
Microsoft.Hosting.Lifetime: Information: Content root path: ...\bin\Debug\net6.0
Host.Triggers.Queue: Warning: Message has reached MaxDequeueCount of 5. Moving message to queue 'queue-poison'.
Expected behavior
Works like beta.1 😛
Actual behavior
Broken.
Known workarounds
Revert back to beta.1.
Related information
To be certain, the above references this package: https://www.nuget.org/packages/Microsoft.Azure.WebJobs.Extensions.Storage
Everything else has been great until this. 😃
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 16 (3 by maintainers)
Commits related to this issue
- https://github.com/Azure/azure-webjobs-sdk/issues/2753 — committed to Mike-E-angelo/Stash by Mike-E-angelo 3 years ago
- Updated WebJobs to beta.5 courtesy of https://github.com/Azure/azure-webjobs-sdk/issues/2753 — committed to DragonSpark/Framework by Mike-E-angelo 3 years ago
Please see https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/storage/Microsoft.Azure.WebJobs.Extensions.Storage.Queues/CHANGELOG.md#500-beta2-2021-02-09 .
Thank you for the information
Apologies, Thank you for the information, I am able to reproduce the issue, I shall discuss this issue internally and update as appropriate
Thank you for the information, we shall investigate this further and update as appropriate