What does the "0.0.0.0" in this Rendezvous retransmission advisory indicate? [2003-02-28 18:30:35]: subject=_RV.INFO.SYSTEM.RETRANSMISSION.OUTBOUND.SENT, message={ADV_CLASS="INFO" ADV_SOURCE="SYSTEM" ADV_NAME="RETRANSMISSION.OUTBOUN

What does the "0.0.0.0" in this Rendezvous retransmission advisory indicate? [2003-02-28 18:30:35]: subject=_RV.INFO.SYSTEM.RETRANSMISSION.OUTBOUND.SENT, message={ADV_CLASS="INFO" ADV_SOURCE="SYSTEM" ADV_NAME="RETRANSMISSION.OUTBOUN

book

Article ID: KB0079301

calendar_today

Updated On:

Products Versions
TIBCO Rendezvous -
Not Applicable -

Description

Question:
What does the "0.0.0.0" in this Rendezvous retransmission advisory indicate?

[2003-02-28 18:30:35]: subject=_RV.INFO.SYSTEM.RETRANSMISSION.OUTBOUND.SENT, message={ADV_CLASS="INFO" ADV_SOURCE="SYSTEM" ADV_NAME="RETRANSMISSION.OUTBOUND.SENT" ADV_DESC="satisfying packet retransmission request" host="0.0.0.0" lost=1}

 

Issue/Introduction

What does the "0.0.0.0" in this Rendezvous retransmission advisory indicate? [2003-02-28 18:30:35]: subject=_RV.INFO.SYSTEM.RETRANSMISSION.OUTBOUND.SENT, message={ADV_CLASS="INFO" ADV_SOURCE="SYSTEM" ADV_NAME="RETRANSMISSION.OUTBOUND.SENT" ADV_DESC="satisfying packet retransmission request" host="0.0.0.0" lost=1}

Environment

Product: TIBCO Rendezvous Version: 6.x.x, 7.x.x OS: All --------------------

Resolution

When a Rendezvous daemon has no data packets to transmit, it periodically sends null packets to maintain continuity.

An incorrectly formed null broadcast packet causes the host address to appear as "0.0.0.0".  We have mostly eliminated this since RV 7.0 by re-writing the null broadcast code to make it more robust.

We still occasionally get reports of these types of advisories and have the following comments to make:

1.  Seeing advisories relating to retransmission is normal in busy networks and usually the host information in the advisory is meaningful.
2.  In a situation, where you do receive such an advisory with "host=0.0.0.0", please be aware that the advisory is still valid and that "host=0.0.0.0" is the only field in the advisory that is incorrect.