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

Cancellation token is not passed to batched event hub function #1626

Closed
paulbatum opened this issue Mar 15, 2018 · 1 comment
Closed

Cancellation token is not passed to batched event hub function #1626

paulbatum opened this issue Mar 15, 2018 · 1 comment
Assignees
Labels
Milestone

Comments

@paulbatum
Copy link
Member

For event hubs, its fairly common for a lease on a partition to be lost. When this occurs, the EventProcessorHost calls CloseAsync on the listener. We fail to pass this cancellation through to the user - see here:

FunctionResult result = await _parent._executor.TryExecuteAsync(input, CancellationToken.None);

This code should be passing through the token.

This is a trivial fix for both v1 and v2.

@paulbatum paulbatum added the bug label Mar 15, 2018
@paulbatum paulbatum added this to the Sprint 19 milestone Mar 15, 2018
@paulbatum paulbatum self-assigned this Mar 15, 2018
paulbatum added a commit to paulbatum/azure-webjobs-sdk that referenced this issue Mar 15, 2018
The same cancellation token should be passed through to user code in both the single dispatch and multi dispatch case.
paulbatum added a commit that referenced this issue Mar 16, 2018
The same cancellation token should be passed through to user code in both the single dispatch and multi dispatch case.
paulbatum added a commit to paulbatum/azure-webjobs-sdk that referenced this issue Mar 16, 2018
The same cancellation token should be passed through to user code in both the single dispatch and multi dispatch case.
@paulbatum
Copy link
Member Author

Both v1 and v2 PRs are merged

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

No branches or pull requests

1 participant