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
Which should refresh keys every 60 minutes, if it fails to fetch them it should retry every 1 minute (not on every request). But Im getting into problems when we are testing that the /pub-keys takes longer to respond, this leads to thread blocking and later it can cause most likely thread starvation - we have encountered problem when the service was not able to receive more requests and the log was filled with vertx thread blocking errors.
Possible improvements
run the HTTP request on the IO thread pool - current implementation uses
simpleHttpGet.get(location);
which is not ideal and runs on vertx event loop and is blocking.
able to set timeout for the request to wait and if fails use the old cache when present.
The text was updated successfully, but these errors were encountered:
I have this configuration:
Which should refresh keys every 60 minutes, if it fails to fetch them it should retry every 1 minute (not on every request). But Im getting into problems when we are testing that the
/pub-keys
takes longer to respond, this leads to thread blocking and later it can cause most likely thread starvation - we have encountered problem when the service was not able to receive more requests and the log was filled with vertx thread blocking errors.Possible improvements
run the HTTP request on the IO thread pool - current implementation uses
which is not ideal and runs on vertx event loop and is blocking.
able to set timeout for the request to wait and if fails use the old cache when present.
The text was updated successfully, but these errors were encountered: