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

The primary worker pool is getting exhausted when the endpoint security is configured #3557

Open
ksankeerth opened this issue Jan 30, 2025 · 0 comments

Comments

@ksankeerth
Copy link

Current Limitation

Currently, there is no way to configure socket timeout, connection timeout and request timeout for oauth token endpoints configured for HTTP endpoints. Therefore, If the token endpoint is slow to connect, the passthrough message processor pool can be exhausted.

Reproducing Steps:

  • Configure an API with oauth protected endpoint and have some token endpoint delay (eg ~5 seconds)
  • Send 500 requests within 1 seconds

Observations

  • Primary passthrough message processor pool will be get exhausted

Suggested Improvement

  • Allow a way to configure socket timeout , request timeout and connection timeout (or introduce some default values to prevent passthrough message processor pool get exhausted)
  • improve current logic to check the token in cache before every new requests is made to to token endpoint

Version

APIM 4.0.0

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

No branches or pull requests

1 participant