Closed danny-krueger closed 1 year ago
@danny-krueger Hi, thank you for reporting, could you please share the .NET version you use
Anyway, I've commited the change (using IHttpClientFactory), if you could verify this somehow before I published a Nuget package, this will be helpful
Hi @Lanayx, thank you for the prompt response. We frequently use .NET 6.0, but occasionally we also use .NET 7.0.
We will try it out, but we need some time to test it.
We have now intensively tested the new variant with IHttpClientFactory. After our testing last weekend, everything looks very good. Can you please create a release from this and provide the new version?
Thank you. I am closing the issue as we believe it has been resolved. If it turns out that it is not fixed, we will reopen the ticket.
Hello all,
unfortunately, from time to time we receive the following error
Unfortunately, we are unable to reproduce the error consistently. It occurs intermittently, typically when there is a network problem or the authentication server is unavailable. Most clients (both consumers and producers) are able to reconnect automatically, as expected. However, some clients remain stuck in the error message mentioned above, resulting in an infinite loop. In such cases, it becomes difficult to identify that the consumer, for example, is no longer able to establish a connection. Moreover, the error only generates a warning. It occurs every minute because there is a one-minute delay before each retry attempt. Unfortunately, authentication always fails during these attempts.
Regarding the issue, we suspect that either the HttpClient is being disposed or the task is being completed, causing the call to the OAuth server to be canceled directly. However, our knowledge of F# is limited, so we would appreciate your assistance in identifying and resolving the problem. You can find the relevant code snippet at this location: GitHub link.
Currently, the only workaround is to restart the entire Kubernetes pod, after which everything returns to normal.
We will continue our efforts to reproduce and resolve the issue. Once we have more information, we will provide updates. If you require any further assistance, please let us know.