When a user leaves cf top running for a long period of time, their UAA refresh token will expire, however we've noticed that it keeps on trying to get a new token. When this occurs we see ~600 requests per minute to UAA's /oauth/token endpoint until the offending user kills their cf top process.
Steps to reproduce the issue
Login to Cloud Foundry cf login
Run cf top
Wait until the refresh token expires
Result: You will see lots of errors being printed to UAA's logs with the message "Handling error: InvalidTokenException, Invalid refresh token expired at..."
Summary
When a user leaves
cf toprunning for a long period of time, their UAA refresh token will expire, however we've noticed that it keeps on trying to get a new token. When this occurs we see ~600 requests per minute to UAA's/oauth/tokenendpoint until the offending user kills theircf topprocess.Steps to reproduce the issue
cf logincf topEnvironment