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

Use SharedExecutorService in more locations #42468

Conversation

alzimmermsft
Copy link
Member

Description

Replaces usage of one-off ExuecutorServices with SharedExecutorService, as most usages of ExecutorService should route through SharedExecutorService as it allows customers more control over the Azure SDK for Java threading story.

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.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

@azure-sdk
Copy link
Collaborator

API change check

API changes are not detected in this pull request.

@alzimmermsft alzimmermsft merged commit 8c639ed into Azure:main Oct 23, 2024
80 checks passed
@alzimmermsft alzimmermsft deleted the AzAll_UseSharedExecutorServiceInMoreLocations branch October 23, 2024 12:42
billwert pushed a commit that referenced this pull request Jan 10, 2025
Use SharedExecutorService in more locations
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Azure.Identity Monitor Monitor, Monitor Ingestion, Monitor Query Search Storage Storage Service (Queues, Blobs, Files) Tables
Projects
Development

Successfully merging this pull request may close these issues.

3 participants