You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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?
The text was updated successfully, but these errors were encountered:
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?
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 usingon(: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?
The text was updated successfully, but these errors were encountered: