-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Do not depend on system clock #121
Comments
Considering this implemented already, closing. |
Over a thousand usages of |
This issue has been automatically marked as stale because it has been a full year without activit. It will be closed if no further activity occurs. Thank you for your contributions. |
Current list in
|
happy to work on that.
? |
This can't be automatic.... a lot of these probably can be changed to use nanotime as they are just intervals, but we also do have real need for wall clock time. For example sessions that are persisted and/or migrated between nodes cannot use nanotime for expiry and have to use a real wall clock. |
We should also consider for Jetty 10 to use |
A PMD rule to check for |
This issue has been automatically marked as stale because it has been a full year without activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has been a |
This is being progressively fixed (see #8067), but will leave open to track progress |
Checking if you're fine to accept a contribution to change from System.currentTimeMillis() to System.nanoTime() in the HttpChannel class In the jvm/application instrumentation library dropwizard metrics, System.nanoTime is used in all scenarios. The only exception where we use System.currentTimeMillis() is to measure jetty request times as the start time is set by jetty. If we can change setting the request time to use System.nanoTime(), we can be consistent in all scenarios. Suggested implementations
|
@dennyac It's not clear to me what the problem is? |
Perhaps it need to be a separately tracked metric? You could use an HttpChannel.Listener.onRequestBegin() to set a Request.attribute with the nanotime as well. Finally, are you sure you want nanotime in the raw like that? |
This issue has been automatically marked as stale because it has been a |
Work completed |
migrated from Bugzilla #413788
status ASSIGNED severity minor in component server for 9.1.x
Reported in version 9.0.4 on platform All
Assigned to: Simone Bordet
On 2013-07-26 05:21:08 -0400, Mikhail Mazursky wrote:
On 2013-09-05 05:49:24 -0400, Simone Bordet wrote:
On 2013-09-05 06:54:07 -0400, Mikhail Mazursky wrote:
The text was updated successfully, but these errors were encountered: