0040994: Store server transition to offline has too long wait time, uses an old preference and can be simplified
Revision
2019-05-31 15:05 by mtaal
Description
The transition to offline process does different kinds of logic during the transition to offline which is not needed as it is already done before going to transition to offline:
- the intervaltime at the customer was set at 10 secs which was below the treshold in the code [6], so transition to offline always took 1 minute which is too long.
- checkoffline handlers [1] is already done here [2]
- it is using a wrong service to check cs availability [3], it should use [4]
- its checks stockmd to see if it is online or offline [5] but the decision to go offline is already made before so can't be repeated as one server can say yes go offline, while another says not can't go offline.
The transition to offline process does different kinds of logic during the transition to offline which is not needed as it is already done before going to transition to offline:
- checkoffline handlers [1] is already done here [2]
- it is using a wrong service to check cs availability [3], it should use [4]
- its checks stockmd to see if it is online or offline [5] but the decision to go offline is already made before so can't be repeated as one server can say yes go offline, while another says not can't go offline.
