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

Removed delay in creating a new session receive link #33856

Merged
merged 1 commit into from
Mar 8, 2023

Conversation

ki1729
Copy link
Contributor

@ki1729 ki1729 commented Mar 3, 2023

Removing fixed delay in retrys after timeout exceptions when creating a new session receive link.
This was fixed in track 1 SDK, but wasn't reflected here. Track 1 issue - Azure/azure-service-bus-java#394

Description

Please add an informative description that covers that changes made by the pull request and link all relevant issues.

If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.

All SDK Contribution checklist:

  • The pull request does not introduce [breaking changes]
  • CHANGELOG is updated for new features, bug fixes or other significant changes.
  • I have read the contribution guidelines.

General Guidelines and Best Practices

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

@ki1729 ki1729 marked this pull request as ready for review March 3, 2023 21:27
@azure-sdk
Copy link
Collaborator

API change check

API changes are not detected in this pull request.

} else if (failure instanceof AmqpException
&& ((AmqpException) failure).getErrorCondition() == AmqpErrorCondition.TIMEOUT_ERROR) {
return Mono.delay(SLEEP_DURATION_ON_ACCEPT_SESSION_EXCEPTION);
return Mono.empty(); // Retry always
Copy link
Member

@anuchandy anuchandy Mar 8, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Per discussion offline with Kishore, when this timeout error happens, it's already the case that there is a backoff completed - Either as a try-timeout on the client or as a delay waiting for service to respond.

Additionally (as mentioned in the pr description) this aligns with what T1 is doing code and git-ticket

@ki1729 ki1729 merged commit 5b16f2d into Azure:main Mar 8, 2023
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.

3 participants