question

Upvotes
Accepted
2 1 1 4

RFA.NET Provider image delivery

We have a provider application developed with RFA.NET 8.0.1.1 that publishes market data on internal feeds. We have recently noticed an issue where quote images published (refreshMsg) after the first are not reaching the client application. Please note that the first image is delivered. The client DataState is OK and the client gets the data updates published without any issue.

I can supply the publisher and subscriber traces . Any ideas what the issue might be ? Is this expected?

treprfarfa-api.net
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvote
Accepted
11.3k 25 8 14

Hi @rbanerjee,

Refresh sent without request from client (after the first one) needs to be set as Unsolicited Refresh.

Normally, Refresh message sent as response to a request is Solicited. If provider application tries to publish Refresh message without request from Consumer, the Refresh messages need to be Unsolicited. The Unsolicited Refresh can be set via the RespMsg.RespTypeNum.

- RDM.INSTRUMENT_REFRESH_RESPONSE_TYPES.REFRESH_SOLICITED = 0
- RDM.INSTRUMENT_REFRESH_RESPONSE_TYPES.REFRESH_UNSOLICITED = 1

Below is the sample code.

respMsg.RespTypeNum = RDM.RDM.INSTRUMENT_REFRESH_RESPONSE_TYPES.REFRESH_UNSOLICITED;
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Thanks. That resolved the issue.

Upvotes
665 3 5 6

Hello @rbanerjee

No this is not expected.If you send unsolicited refreshes subsequent to the first (Solicited) refresh then any subscribing client should receive it. This might happen if a provider omits one or more attributes that are mandatory for a refresh in the subsequent unsolicited refreshes. If you can provide trace files I will take a look.

NnjjuNnn

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.