What is the meaning of the following TIBCO Rendezvous® (RV) log file message: “system time advanced by approximately XXX”.
Article ID: KB0088011
Updated On:
| Products | Versions |
|---|---|
| TIBCO Rendezvous | - |
| Not Applicable | - |
Description
Resolution:
Description:
============
The message indicates that the system clock has been changed while the rvd/rvrd daemon was running.
The system clock is read at startup and used to calculate numerous timer offsets. If the system clock is changed during runtime, these timers which are used extensively within rvd/rvrd will not work properly. The API (especially CM and others) will also not function properly.
TIBCO Rendezvous, as a real-time messaging system, relies heavily on timers. RV daemons use timers in many different ways. One such example of how timers are important is that in the daemon itself, timers determine how many outbound messages to retain for the reliability interval. Another example is in the API, timers expire messages from the CM ledger. Having timers not firing properly will therefore have a negative impact on both reliable and certified transmission of messages.
If timers are not firing correctly, messages may not become expired as they should after 60 seconds by default. Such messages will be queued in the daemon for retransmission purposes. As a result, as more messages are queued in the daemon, memory usage will increase.
With an RVRD configured to connect to many neighbors, the effect can be great due to RVRDs trying to resync with each other.
Resolution:
= = = = = =
A workaround does exist in the case where the system clock is changed. RV daemons and mission-critical applications should be stopped before and restarted after changing the system time.
Description:
============
The message indicates that the system clock has been changed while the rvd/rvrd daemon was running.
The system clock is read at startup and used to calculate numerous timer offsets. If the system clock is changed during runtime, these timers which are used extensively within rvd/rvrd will not work properly. The API (especially CM and others) will also not function properly.
TIBCO Rendezvous, as a real-time messaging system, relies heavily on timers. RV daemons use timers in many different ways. One such example of how timers are important is that in the daemon itself, timers determine how many outbound messages to retain for the reliability interval. Another example is in the API, timers expire messages from the CM ledger. Having timers not firing properly will therefore have a negative impact on both reliable and certified transmission of messages.
If timers are not firing correctly, messages may not become expired as they should after 60 seconds by default. Such messages will be queued in the daemon for retransmission purposes. As a result, as more messages are queued in the daemon, memory usage will increase.
With an RVRD configured to connect to many neighbors, the effect can be great due to RVRDs trying to resync with each other.
Resolution:
= = = = = =
A workaround does exist in the case where the system clock is changed. RV daemons and mission-critical applications should be stopped before and restarted after changing the system time.
Issue/Introduction
What is the meaning of the following TIBCO Rendezvous® (RV) log file message: “system time advanced by approximately XXX”.
Feedback
Yes
No
Powered by
