Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RateLimit Change: Use nanoTime time instead of currentTimeMillis #2105

Merged
merged 2 commits into from
Nov 28, 2022

Conversation

strehle
Copy link
Member

@strehle strehle commented Nov 21, 2022

Main Change: System::currentTimeMillis moved to System::nanoTime
Others are mostly rename to make it transparant that we use internally nano time.

In stackoverflow and others I have read, that currentTimeMillis has issues in cases we have, means, if a process goes into sleep mode and awaks.

@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/183853023

The labels on this github issue will be updated when the story is started.

Copy link
Contributor

@swalchemist swalchemist left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested this all day yesterday, and it's looking good.

@strehle
Copy link
Member Author

strehle commented Nov 23, 2022

@strehle strehle added this to the 76.5.0 milestone Nov 23, 2022
@strehle strehle merged commit 5f75ed7 into develop Nov 28, 2022
@strehle strehle deleted the fix/issue/2081 branch November 28, 2022 21:44
strehle added a commit that referenced this pull request Mar 3, 2023
Use nano time for IT
Why: see infinite loops in tests and these might be resulted because of the VM and behaviour of this timeout check
if vm goes into a suspend mode (only for a short time) and awakes then the time comparison can be a problem and this
could explain the infinite loop. Saw similar things in #2105
@strehle strehle mentioned this pull request Mar 3, 2023
strehle added a commit that referenced this pull request Mar 3, 2023
Use nano time for IT
Why: see infinite loops in tests and these might be resulted because of the VM and behaviour of this timeout check
if vm goes into a suspend mode (only for a short time) and awakes then the time comparison can be a problem and this
could explain the infinite loop. Saw similar things in #2105
@cf-gitbot cf-gitbot added delivered accepted Accepted the issue and removed delivered labels Jun 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted Accepted the issue
Projects
Development

Successfully merging this pull request may close these issues.

LimiterExpirationProcess error repeated infinitely when a UAA server goes idle
3 participants