-
Notifications
You must be signed in to change notification settings - Fork 234
OpenJDK Server VM warning: No monotonic clock was available - timed services may be adversely affected if the time-of-day clock changes #469
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
Comments
Can you please check if you see the same behaviour with a ubuntu:20.04 image ? |
and
|
I meant to run |
|
@aahlenst thanks ! ... That confirms that it is a Ubuntu 20.04 issue. |
Sorry, that I couldn't reply faster. |
Guy from ubuntu image project helped me and I was able to solve this issue by updating |
When I run a docker image built from
adoptopenjdk:15-jdk-hostspot
on my raspberry pi 3B (arm32v7
architecture) and start any java application inside a container, I get the following warning:OpenJDK Server VM warning: No monotonic clock was available - timed services may be adversely affected if the time-of-day clock changes
At least theses versions are also affected:
14-jdk-hostspot
11-jdk-hostspot
When I execute
date
inside a container multiple times, it prints the following random dates:Thu 19 Feb 1970 02:46:19 PM UTC
Thu 19 Feb 1970 11:54:27 PM UTC
Tue 24 Feb 1970 03:22:35 PM UTC
Tue 03 Mar 1970 03:15:07 PM UTC
When I execute "date" directly in my raspberry pi OS, it prints the following correct dates:
Wed 18 Nov 21:17:42 EET 2020
Wed 18 Nov 21:17:43 EET 2020
Wed 18 Nov 21:17:44 EET 2020
Wed 18 Nov 21:17:51 EET 2020
Moreover, my springboot applications inside a container also starts only randomly. Most of the time it simply does not start, only mentioned warning is printed in logs. But the same application starts and operates correctly when I run it directly from raspberry pi OS.
One more thing: when I run for example
tomcat:7-jdk8-adoptopenjdk-hotspot
image and executedate
command, it prints date correctly. Same applies toalpine
image. So it shows, that this is not a hardware or raspberry pi OS issue.The text was updated successfully, but these errors were encountered: