question

Upvotes
Accepted
3 0 0 3

Item values are not updated after NI Provider restart

We currently develop the NI Provider application that publishes quotes with the MMT_MARKET_PRICE domain.

The problem is after the provider restarts and sends refresh messages, the consumer is not able to update item values. We tried to keep the same handle value for the item between restarts and change it - doesn't help.

We cannot change the consumer logic. In OMMViewer we also observe items disappear after provider restarts and we have to open a new subscription. So the question is if there's something wrong with our provider logic? Can we change it somehow to get rid of consumer restart? Is it necessary to have the same handle value in refresh messages for the same item in different provider sessions?

Below is the source code of the provider (in kotlin):

val refreshMsg = EmaFactory.createRefreshMsg()
refreshMsg.serviceName(serviceName).name("FIAT_" + trepQuoteDTO.isin)
refreshMsg.domainType(MMT_MARKET_PRICE)
refreshMsg.state(
		OmmState.StreamState.OPEN,
		OmmState.DataState.OK,
		OmmState.StatusCode.NONE,
		"UnSolicited Refresh Completed")
val fieldList = EmaFactory.createFieldList()


fieldList.add(EmaFactory.createFieldEntry().ascii(831, serviceName))
fieldList.add(EmaFactory.createFieldEntry().real(BID, trepQuoteDTO.bid, OmmReal.MagnitudeType.EXPONENT_NEG_2))
fieldList.add(EmaFactory.createFieldEntry().real(BID_SIZE, trepQuoteDTO.bidSize, OmmReal.MagnitudeType.EXPONENT_0))
fieldList.add(EmaFactory.createFieldEntry().real(ASK, trepQuoteDTO.ask, OmmReal.MagnitudeType.EXPONENT_NEG_2))
fieldList.add(EmaFactory.createFieldEntry().real(ASK_SIZE, trepQuoteDTO.askSize, OmmReal.MagnitudeType.EXPONENT_0))
refreshMsg.payload(fieldList).complete(true)
val handleId: Long = itemHandlers.getOrPut(trepQuoteDTO.isin, { counter.getAndIncrement() })
provider.submit(refreshMsg, handleId)
elektronrefinitiv-realtimeelektron-sdkrrtema-apielektron-message-apinon-interactive-providerrefresh
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.

Upvotes
Accepted
16.7k 42 12 19

Hi @askochin, You can publish the item on the same handle in between the restarts.

I tried the Java EMA sample example100__MarketPrice__Streaming and connected the OMMConsumer, and the application was able to receive refresh and update messages after multiple NIP restarts.

Can you please try the Java sample instead of Kotlin? Also, in you code, you seem to be sending refreshes only.

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.

Upvotes
3 0 0 3

@Gurpreet., thanks! We send updates after refreshes only so they work ok.

Looked at the config in examples, it's quite the same as ours.

The problem was our NIP started sending refreshes after restart with the delay.

If this delay is less than 10-15 sec, OMMViewer recovers the item value and updates DataState from SUSPECT to OK.

Otherwise, if this timeout expires, it considers the item to be "Not In Cache". And all this doesn't depend on whether handle is the same or not after restart.

Does anybody know if there's a config param setting this delay? Is the handle value supposed to be used in update messages only?

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.

Upvotes
16.7k 42 12 19

So, to be sure, you are using a non interactive provider, and publishing into the ADH cache, and subscribing to that data from ADS, right?

There are numerous parameters within TREP configuration which control the service behavior, when the provider goes down. Its advisable to work with your market data administrator to get it properly setup.

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.

Yes, we use a non interactive provider, and publish into the ADH cache, and subscribe from ADS

Upvotes
1 0 0 0

@Gurpreet. Can you please kindly have a look at the attached rmds.zip (rmds.cnf) So we will change parameters if it is required for client needs


rmds.zip (6.1 KiB)
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.