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

"read would block" when communicating with external APIs #317

Open
gillesbergerp opened this issue Sep 29, 2024 · 5 comments
Open

"read would block" when communicating with external APIs #317

gillesbergerp opened this issue Sep 29, 2024 · 5 comments

Comments

@gillesbergerp
Copy link

gillesbergerp commented Sep 29, 2024

Basic Info

  • Faraday Version: 2.11.0
  • Ruby Version: jruby 9.4.8.0 (3.1.4) 2024-07-02 4d41e55a67 OpenJDK 64-Bit Server VM 21.0.4+7-LTS on 21.0.4+7-LTS +jit [x86_64-linux]
  • JRuby OpenSSL Version: 0.15.0

Issue description

We occasionally and intermittently face Faraday::SSLErrors with the message read would block when communicating with external endpoints. Our application is deployed as an ECS on EC2 service and (so far) we were unable to reproduce the issue locally or in our staging environment.

Steps to reproduce

Unfortunately, we haven't managed to reproduce the issue locally. There are certain requests to external APIs that fail very consistently, however.

@jpsikorra
Copy link
Contributor

jpsikorra commented Oct 21, 2024

We also ran into this problem, it seems like switching from TLS 1.3 to TLS 1.2 mitigates the issue at least sometimes.

@gillesbergerp
Copy link
Author

@jpsikorra, when you say "sometimes", do you suggest that it doesn't occur anymore at all for some sites/endpoints (but still does for others) or that the overall rate is lower?

@jpsikorra
Copy link
Contributor

I don't see the issue with TLS 1.2, but cannot be 100% certain that it will never occur.

@jpsikorra
Copy link
Contributor

Also see #305

@gillesbergerp
Copy link
Author

I can confirm that we had success with switching to TLS 1.2 for one external API as well

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

No branches or pull requests

2 participants