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
We use the MGW 3.2.0/3.2.1, and recently found a problem that comes up with a lot of frequency.
When the number of concurrent requests reaches a certain level, http 500 will be returned to the request API, and the returned information is
{"fault":{"code":900900, "message":"Unclassified Authentication Failure", "description":"Unclassified Authentication Failure. Unclassified Authentication Failure"}}".
Please help me on this question. Thanks!
Steps to Reproduce
We changed the following configuration in micro-gw.conf, tokenCacheExpiryTime = 86400
[caching] tokenCacheExpiryTime = 60
tokenCacheCapacity = 10000
tokenCacheEvictionFactor = 0.25
however, a 900900 error was still found in the test.
We tried refreshing the Access Token to avoid this exception, but it didn't work either. He still reappears, just less often.
Version
MGW 3.2.0/3.2.1
Environment Details (with versions)
docker
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response
The text was updated successfully, but these errors were encountered:
Description
We use the MGW 3.2.0/3.2.1, and recently found a problem that comes up with a lot of frequency.
When the number of concurrent requests reaches a certain level, http 500 will be returned to the request API, and the returned information is
{"fault":{"code":900900, "message":"Unclassified Authentication Failure", "description":"Unclassified Authentication Failure. Unclassified Authentication Failure"}}".
Please help me on this question. Thanks!
Steps to Reproduce
We changed the following configuration in micro-gw.conf, tokenCacheExpiryTime = 86400
[caching]
tokenCacheExpiryTime = 60
tokenCacheCapacity = 10000
tokenCacheEvictionFactor = 0.25
however, a 900900 error was still found in the test.
We tried refreshing the Access Token to avoid this exception, but it didn't work either. He still reappears, just less often.
Version
MGW 3.2.0/3.2.1
Environment Details (with versions)
docker
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response
The text was updated successfully, but these errors were encountered: