Skip to content

Conversation

@alexdawes
Copy link

Description

Currently, the _consumerCache within the ConsumerFactory has bad IBasicConsumer's removed and swapped out for new ones. This mechanism uses the Task.IsCompleted method (https://docs.microsoft.com/en-us/dotnet/api/system.threading.tasks.task.iscompleted?view=net-6.0), which catches cancelled and faulted tasks as well. However, if the task is faulted/cancelled, then calling Task.Result on such a task will result in the error (or TaskCanceledException) to be thrown.

Because of this, if the task in the cache becomes cancelled or faulted for whatever reason (I experienced this myself with a cancelled task, though have no idea where it came from) then the error will remain in the cache and be thrown whenever the consumer for that key is retreived again

This PR is a simple change to the logic to treat faulted and cancelled tasks separately to successfully completed tasks.

@VladProkopovich
Copy link

@pardahlman Can you please take a look?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants