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

[ServiceBus] Settlement API may not return or throw error if try timeout is long #22299

Closed
YijunXieMS opened this issue Jun 15, 2021 · 0 comments · Fixed by #22317
Closed

[ServiceBus] Settlement API may not return or throw error if try timeout is long #22299

YijunXieMS opened this issue Jun 15, 2021 · 0 comments · Fixed by #22317
Assignees
Labels
amqp Label for tracking issues related to AMQP Service Bus
Milestone

Comments

@YijunXieMS
Copy link
Contributor

ServiceBusReactorReceiver.updateDisposition does not return or throw error if try timeout is long (from about 50 seconds but no exact number, usually 10 seconds is safe) and network is down.
This is because when try timeout is long enough, ServiceBusReactorReceiver.updateDisposition() hasn't timed out while another thread closes the ServiceBusReactorReceiver and therefore causes the updateDisposition not to finish.

@YijunXieMS YijunXieMS added the amqp Label for tracking issues related to AMQP label Jun 15, 2021
@YijunXieMS YijunXieMS added this to the [2021] July milestone Jun 15, 2021
@YijunXieMS YijunXieMS self-assigned this Jun 15, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
amqp Label for tracking issues related to AMQP Service Bus
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant