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

Proper Handling for Errors (e.g. SSL Expired) #119

Open
ksylvest opened this issue Apr 19, 2022 · 1 comment
Open

Proper Handling for Errors (e.g. SSL Expired) #119

ksylvest opened this issue Apr 19, 2022 · 1 comment

Comments

@ksylvest
Copy link

Our application recently encountered an issue with Sidekiq processes crashing due to an expired APN certificate. The root of this issue appears to have stemmed from the usage of abort_on_exception within the dependent HTTP-2 library.

Per the author, the abort_on_exception is problematic when used with Sidekiq. To fix, our team is investigating using on(:error) { |exception| ... } callback fixes the process crashes per your documentation (https://github.com/ostinelli/apnotic#methods).

It appears that this causes the thread to hang until some sort of internal timeout is resolved. Is it possible to stop execution when an error is encountered safely without killing the parent thread?

@Linuus
Copy link

Linuus commented Apr 11, 2024

It appears that this causes the thread to hang until some sort of internal timeout is resolved. Is it possible to stop execution when an error is encountered safely without killing the parent thread?

Related to ostinelli/net-http2#52 ?

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