Marcellus AD.03116 (Customer) asked a question.
Okta Server cutting connections unexpectedly
Hello,
I'm investigating an issue in my application server logs, and I can see several entries related to abrupt connection interruptions before an Okta API response (an average of 10x/day). We're using the Pekko HTTP library (1.2.0) for performing API calls to Okta.
The stack trace follows the pattern below:
Okta request failed due to [The HTTP server closed the connection unexpectedly before delivering responses for 1 outstanding requests], retrying in [229 milliseconds]. Entity [None]
I'm looking for an explanation for this behavior and if it could be prevented from the client side. Any insights are appreciated.
Thanks
Hello @Marcellus AD.03116 (Customer) Thank you for posting on our Community page!
The log you shared seems to be on the application side. Were you able to find anything in the Okta logs? Could the issue be that you are reaching the Rate limits on Okta side and this unable to make any more calls for 1 min?
This question is more appropriate for our dedicated Okta Developer Forum.
My advice would be to reach out via devforum.okta.com to take advantage of their expertise.
While we'll do our best to answer all of your questions here, this medium is more inclined towards Okta core products and features (non-developer work).
Thank you for reaching out to our Community and have a great day!
--
Help others in the community by liking or hitting Select as Best if this response helped you.
Hi Paul, thanks for responding.
Unfortunately I can't see any meaningful logs on the Okta side. I'm relatively confident that it does not fall into rate-limit denials because the Okta server does not respond to the request, it simply ends the connection.
We're currently implementing retries when we get such errors and they are usually effective.
I'm wondering if this is part of a regular server-side operations for recycling connections, or other network issues.
I've opened a topic on the devforum as you suggested, Paul. Thanks