Hello everyone,
we recently encountered significant issues related to Eclipse Amlen and a configured OAuth service in one of our endpoints:
The external OAuth2 server experienced problems, which caused the response times of the OAuth2 server configured in the endpoint for token validation to increase from 0ms to suddenly 15 seconds.
We have ~9,500 clients validating against the OAuth2 server.
As a result, Eclipse Amlen stopped accepting new connections, even from other applications not using OAuth, because the 9.5K clients did not receive a timeout and their connections were held open.
Is there a way to make the software more resilient in this scenario, perhaps by setting a timeout within the OAuth configuration? I couldn’t find a parameter for this in the Amlen configuration.
Alternatively, can I set the timeout somewhere else? Are there any best practices for this?
Thank you very much.
Best regards
Enrico
Hello everyone,
we recently encountered significant issues related to Eclipse Amlen and a configured OAuth service in one of our endpoints:
The external OAuth2 server experienced problems, which caused the response times of the OAuth2 server configured in the endpoint for token validation to increase from 0ms to suddenly 15 seconds.
We have ~9,500 clients validating against the OAuth2 server.
As a result, Eclipse Amlen stopped accepting new connections, even from other applications not using OAuth, because the 9.5K clients did not receive a timeout and their connections were held open.
Is there a way to make the software more resilient in this scenario, perhaps by setting a timeout within the OAuth configuration? I couldn’t find a parameter for this in the Amlen configuration.
Alternatively, can I set the timeout somewhere else? Are there any best practices for this?
Thank you very much.
Best regards
Enrico