View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0003110||SymmetricDS||Bug||public||2017-05-15 12:54||2023-05-25 19:57|
|Status||closed||Resolution||unable to reproduce|
|Summary||0003110: If you set the time in the past on a machine hosting SymmetricDS, the heartbeat job doesn't run until you pass that time again|
|Description||If you set the time in the past on a machine hosting SymmetricDS, the heartbeat job doesn't run until you pass that time again|
||This happens because Spring uses timers that compare the current time with the scheduled time. The call to Thread.sleep() appears to be immune to the problem, so we could have a thread that constantly checks to see if time has gone backwards since the last check and calls engine.getJobManager().restartJobs().|
cannot reproduce; heartbeat job continues to run correctly according to its set period regardless of changes to the system time or time zone.
The "last finish time" is even automatically adjusted to the correct time when a change is made directly to the system time.
The "last finish time" is NOT automatically adjusted to the correct time when a change is made to the system time zone, but as mentioned previously, the heartbeat job continues to run correctly according to its period anyways.
|2017-05-15 12:54||chenson||New Issue|
|2017-05-15 12:54||chenson||Status||new => assigned|
|2017-05-15 12:54||chenson||Assigned To||=> chenson|
|2017-05-15 12:55||chenson||Assigned To||chenson => maxwellpettit|
|2019-04-25 20:20||elong||Tag Attached: jobs|
|2019-05-22 19:48||elong||Assigned To||maxwellpettit =>|
|2019-05-22 19:48||elong||Status||assigned => confirmed|
|2019-05-22 19:48||elong||Note Added: 0001504|
|2020-09-03 12:56||admin||Tag Detached: jobs|
|2022-08-02 19:25||elong||Tag Attached: job manager|
|2023-05-25 19:57||JishLong||Status||confirmed => closed|
|2023-05-25 19:57||JishLong||Resolution||open => unable to reproduce|
|2023-05-25 19:57||JishLong||Note Added: 0002335|