Unexpected status received on Update message.

LtDoolittle6
LtDoolittle6 Contributor
in RFA

We get
strange behavior from the RFA.NET API. After our application successfully subscribe to this RIC (Subscription sent with handle:
248094503616), it get a Refresh message with StreamState = Open |
DataState = Ok. Then, we get all sorts of combinations, all for RespType
= Update:

a.StreamState = UnspecifiedStreamState |
DataState = Suspect

b.StreamState = NonStreaming | DataState =
Ok

c.StreamState = Open | DataState = Ok

d.StreamState = Closed | DataState = Suspect

How should
we handle these statuses? The biggest issue we have is on the last status: StreamState = Closed | DataState = Suspect which means
that data is not valid.

Tagged:

Best Answer

  • veerapath.rungruengrayubkul
    veerapath.rungruengrayubkul LSEG
    Answer ✓

    Hi,

    The Update response
    message (RespType=Update) doesn’t support RespStatus, so retrieving RespStatus from Update response could return unexpected result. Application should not get
    RespStatus from the Update response. Instead, it can monitor
    status of item via the RespStatus of Refresh (RespType=Refresh) or Status (RespType=Status) response message.

    For example, the Stale status
    (DataStream=”Suspect” and StreamState=”Open”) for API generally means that
    current data is out of date or cannot be confirmed as current. If a stale
    status is received even in Refresh or Status, all data of the
    item should be marked as stale data.

Categories