View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001545 | SymmetricDS | Improvement | public | 2014-01-23 20:26 | 2014-02-05 15:08 |
Reporter | Assigned To | chenson | |||
Priority | normal | ||||
Status | closed | Resolution | fixed | ||
Product Version | 3.5.15 | ||||
Target Version | 3.5.16 | Fixed in Version | 3.5.16 | ||
Summary | 0001545: Unlock should use symmetricds server time, not database time, for consistency. | ||||
Description | If the database time and server time are mismatched, you can run into the issue where, after a restart, the jobs (route, for example), might not run for quite some time. This can happen when the database time is in the future relative to the server's time. This happens only at startup, and only when there's existing entries in sym_lock wiht future dates shown. The "fix" is to change the unlock update query to use the server time, not current timestamp from the database. | ||||
Tags | No tags attached. | ||||
SymmetricDS: master e1d23dcf 2014-01-23 19:11:15 Details Diff |
0001545: Unlock should use symmetricds server time, not database time, for consistency. |
Affected Issues 0001545 |
|
mod - symmetric-core/src/main/java/org/jumpmind/symmetric/service/impl/ClusterService.java | Diff File | ||
mod - symmetric-core/src/main/java/org/jumpmind/symmetric/service/impl/ClusterServiceSqlMap.java | Diff File |
Date Modified | Username | Field | Change |
---|---|---|---|
2014-01-23 20:26 |
|
New Issue | |
2014-01-23 20:26 |
|
Status | new => assigned |
2014-01-23 20:26 |
|
Assigned To | => chenson |
2014-01-24 00:11 | chenson | Status | assigned => resolved |
2014-01-24 00:11 | chenson | Fixed in Version | => 3.5.16 |
2014-01-24 00:11 | chenson | Resolution | open => fixed |
2014-02-03 01:53 | Changeset attached | => SymmetricDS trunk r7888 | |
2014-02-05 15:08 | chenson | Status | resolved => closed |
2015-07-31 01:49 | chenson | Changeset attached | => SymmetricDS master e1d23dcf |