@vijay.rao1

I think the SuspectEnum you received is just default value that RFA set in the RespStatus object. Actually the Update message type does not contains Response Status. It just like the MarketPrice domain spec.

Basically applications can identify whether or not the Response Message contains RespStatus by retrieving the Hint mask using getHintMask() and checking the value against RespStatusFlag. Our example such as StarterConsumer use this approach to verify if the response message contains RespStatus before print it to console.

if(respMsg.getHintMask() & RespMsg::RespStatusFlag)
{
    const RespStatus& status = respMsg.getRespStatus();
    //... Shows Response Status
}

Not sure have you added the codes to check RespStatusFlag before you get the RespStatus ?

We do perform that AND operation on getHintMask prior to checking the status. We can stream out the status and I'm currently trying to capture the 'suspect' status. Looks like status has a stream operator defined. On startup we get:

(1) Status : None, Text : All connections Pending, Stream : Open, Data : Suspect

Then our initial login fails which seems to be expected behavior:

(2) Status : None, Text : All connections Pending, Stream : Open, Data : Suspect

(3) Status : None, Text : Source unavailable... will recover when source is up, Stream : Open, Data : Suspect

Then the login succeeds:

(4) Status : None, Text : Login accepted by host EDGE...., Stream : Open, Data : Ok

(5) Status : None, Text : All is well, Stream : Open, Data : Ok

After that we only receive the following message for each incoming message:

(6) Status : None, Text : All is well, Stream : Open, Data : Ok

I suspect something happens after running for some time that causes a resubscribe which causes responses (1) through (3) to reoccur. I'm currently logging output in the hopes of encountering this condition.

Thanks