Support #623
Updated by Madars over 3 years ago
Currently tpridge exchanges monotonic clock values when connection is established between nodes. This value is used for detection of expired in progress messages, and if they are expired, message is dropped automatically when - NDRX_LOG(log_debug, "Received call reaches server process. If the clocks on servers over the time drift away (thus the difference after some 15 days, is not more X seconds, stored in bridge, but Y seconds), and if this difference is higher than NDRX_TOUT setting, then it is possible that messages received from other server node are never processed and dropped immediately. Thus already expired! call age = %ld s, client timeo.... -> Change to cope with this situation:
log_error (and maybe add msg to ULOG too)
- Periodic exchange of monotonic server Bridge do clock value shall be implemented.
- Only if the exchange sync at idle time is less than certain time, the new calculated difference should be used.
instead of zero len msg (new cli flag?)
- Also when messages are dropped for this reason, they should go maybe add some command to ULOG print all bridge clocks, local monotonic clock, our vision of remote clock and in process log logged with error level 2. delta
log_error (and maybe add msg to ULOG too)
- Periodic exchange of monotonic server Bridge do clock value shall be implemented.
- Only if the exchange sync at idle time is less than certain time, the new calculated difference should be used.
instead of zero len msg (new cli flag?)
- Also when messages are dropped for this reason, they should go maybe add some command to ULOG print all bridge clocks, local monotonic clock, our vision of remote clock and in process log logged with error level 2. delta