Requests are sent with ack received,but symbol not updated

khycelyn.esquivel
khycelyn.esquivel LSEG
in WebSocket API

Client is contributing via RCC API using websocket, and facing intermittent issues where some requests are sent with ack received, but RICs are not updated. They sent the following message with value null to CLEAR the value 5.Message was received and acknowledged, but value not cleared. [SENT]: 20240512 15:40:02.247|1|Info|> {"Ack":true,"Key":{"Name":"SGNZ19100S=NITS","Service":"DDS_TRCE"},"Type":"Post","Message":{"Type":"Update","ID":2,"Fields":{"SEC_VOL1":null} },"PostID":62,"ID":1,"Domain":"MarketPrice"} [RECEIVED]: 20240512 15:40:02.403|1|Info|< [{"ID":1,"Type":"Ack","AckID":62}] So an ‘update’ request with null value was sent to clear off Offer Size (SEC_VOL1) of RIC but request was acknowledged and successful, but not updated in system. [REQUEST] - 20240520 01:06:29.432|1|Info|> {"Ack":true,"Key":{"Name":"SGN520100A=NITS","Service":"DDS_TRCE"},"Type":"Post","Message":{"Type":"Update","ID":2,"Fields":{"SEC_VOL1":null} },"PostID":162,"ID":1,"Domain":"MarketPrice"} [RESPONSE] - 20240520 01:06:29.629|1|Info|< [{"ID":1,"Type":"Ack","AckID":162}] I wonder if this is an expected behavior on websocket api side or product bug?

Tagged:

Best Answer

  • Gurpreet
    Gurpreet admin
    Answer ✓

    Hello @khycelyn.esquivel,

    The null value might be an invalid entry for this field - considering it is a volume field. But, the server should have responded with a NACK instead. I would recommend that you raise this directly with the RCC product support.

Categories