addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscontroller-playcredit-cardcrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobe--smallglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1launch-new-window--smalllight-bulblinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonprintShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

Re: [ljc] JVM is messed up when system clock is rolled backward

From: Richard W.
Sent on: Thursday, September 5, 2013 11:00 AM

I guarantee we do not have sleep() to synchronize things :), we are using java.concurrency primitives. The most problematic thing is the ScheduledExecutor: it just stops. The backup plan would be 1) patch the JVM or 2) rewrite in native some of those function but I am afraid of the extent of this issue. LockSupport.parkNanos(..) is basically the root of all other concurrency primitives in the JVM.

It'll be heavily used in the concrete concurrency classes, but not by the actual synchronized keyword.


  Dr. Richard Warburton

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy