Description:
A defect is identified regarding a TRDP sequence rollover in RV 8.2+ daemons. This defect affects only TRDP daemons, PGM daemons are not impacted by this defect.  

Each UDP service used for publishing by a RV daemon has its own TRDP packet sequence number. Due to this defect, when the TRDP packet sequence number rolls over for a publishing RV 8.2+ daemon, the receiving daemon(s) are no longer being made aware of the TRDP packet sequence rollover. Thus, all subscribing RV clients will stop receiving messages from the publishing daemon as the receiving daemon(s) start viewing the lower sequenced TRDP packets after a sequence rollover as old/retransmitted packets and discard it. This leads to unreported dataloss.

All variants RV 8.2+ TRDP daemons (RVD, RVRD, RVSRD, RVSD) are affected by this defect.
This defect is fixed in the RV 8.3.1 version.

In case it is not possible to upgrade to RV8.3.1 right away and data rates are such that daemon might send more than 4 billion packets during a single process lifetime, to work-around this issue, it is recommended to restart TRDP RV8.2+ daemons periodically.

The HOST.STATUS advisory field “ps” (Packets Sent) can be used to see if it is safe to keep the daemon running. The “ps” value could be higher than the actual sequence for which the safe higher value could be 4000000000, soon after which you could schedule a restart of the daemon.

TRDP (TIBCO reliable datagram protocol) packet sequence rollover leads to unreported dataloss for RV (Rendezvous) 8.2+ TRDP daemons