Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've got a ESXI-Server and a OpenSuse 10.3 distribution running on it as a guest system. In a java (6_17) application that uses Thread.sleep() to not hog 100% CPU, I noticed that it sometimes never wakes up again, and the application is in a coma. I started logging before going to sleep and noticed that the clock jumps one hour and a few minutes ahead, and the time logged shortly afterwards from some other thread produces the real time again.

There are some Java bugs posted, that all drill down to Linux using the wrong clock to sleep. There are also some virtual machine issues with jumping time. Has someone seen something similar, so I know where I shall start searching?

Even Object.wait() is broken, therefore I can't even shut my application down neatly. Can calling Thread.sleep() to often trigger to many time update from the hareware?

share|improve this question
What kernel-version is that? – Nils Nov 23 '12 at 21:11

Here's a few things to try:

  1. Make sure that you have vmware tools installed.
  2. Read the Timekeeping in VMware Virtual Machines document.
  3. Read the Knowledge Base Article: Timekeeping best practices for Linux guests This has settings specific for SUSE.

Personally, I've found that sleep works reliably with java (1.6.0_16) with VMWare tools providing the time synchronisation but that's been on Redhat and Solaris VM's rather than Suse. The 2 documents above should help.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.