I should also say that another Java program is also running under the
same Server VM, to which I also provide the ForceTimeHighResolution VM
flag, so that all Java VM's running on the system have that, which is
supposedly the "fix" to the Bug. So I cannot say whether the system
clock alteration comes from my own code or the other Java code which
is not mine. Windows time synchronization service is switched OFF, so
once I synch the clock I assume the only alteration will be due to
Java execution.
On Oct 30, 8:19 am, FutureScalper <futurescal...@[EMAIL PROTECTED]
> wrote:
> This bug has been present way back, and has never been fixed.
>
> Running the Hotspot Server VM Java 6 Update 3, I am getting seriously
> accelerated system clock times which can be as much as a minute over a
> couple of hours.
>
> Gateway GT5636E Quad processor Windows Vista Home Premium OS.
>
> This is just unacceptable for Java to have the side-effect of altering
> the system clock.
>
> I have removed ALL Thread.sleep calls and have created my own facility
> using wait, as the bug was originally with the sleep call. This helps
> most of the time, but there is still an alteration of the windows
> system clock.
>
> It has something to do with Java moving the system clock back so that
> threads which are waiting on time will be awakened.
>
> Yes, I use the ForceTimeHighResolution argument to the VM... Doesn't
> fix it, apparently under all cir***stances.
>
> I provide the argument under Java Web Start, and can only assume it
> gets passed properly to the underlying VM.
|
