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
It affects both quarkus-oidc and quarkus-oidc-client - if the connection error has happened after the initial connection was established, for ex, the connection was dropped, then, as recommended by Clement, it makes sense to retry.
Implementation ideas
I've seen this Connection was closed only once, today, so it is quite rare - but for the moment I'll just add say 3 retries with a 1/2 sec delay between the retries, which should be sufficient - later on we can also configure it better - but for now I'd like to avoid users configuring for ex a 5 secs delay between the retries or retry for 1 min etc
CC @cescoffier
The text was updated successfully, but these errors were encountered:
Description
It affects both
quarkus-oidc
andquarkus-oidc-client
- if the connection error has happened after the initial connection was established, for ex, the connection was dropped, then, as recommended by Clement, it makes sense to retry.Implementation ideas
I've seen this
Connection was closed
only once, today, so it is quite rare - but for the moment I'll just add say 3 retries with a 1/2 sec delay between the retries, which should be sufficient - later on we can also configure it better - but for now I'd like to avoid users configuring for ex a 5 secs delay between the retries or retry for 1 min etcCC @cescoffier
The text was updated successfully, but these errors were encountered: