Stream closed without request
We use RFA 8.NET consumer
After having noticed that some of our symbols had stopped updating we enabled tracing in the application. The trace indicates the stream was closed even though it was not requested by the application ( we can observe from separate application logs). There are several of these messages for various streams.
<!-- Outgoing Message to 'gcm-ads-r1:14002' on 'localhost' interface -->
<!-- Time: 11:20:29:781 -->
<!-- rwfMajorVer="14" rwfMinorVer="0" -->
<closeMsg domainType="RSSL_DMT_MARKET_PRICE" streamId="806" containerType="RSSL_DT_NO_DATA" flags="0x0" dataSize="0">
<dataBody>
</dataBody>
</closeMsg>
In what other scenarios would the stream be closed ( these are not Bad symbols ) when the application has not request . How do we detect that?
Thanks
Raja
Best Answer
-
From the trace file, we could see that closed messages have been sent by the application.
A closed message can be sent by the following calls.
- UnregisterClient(itemHandle);
This closes the stream of the supplied itemHandle.
- UnregisterClient();
This close all streams that were opened for an OMMConsumer.
- OmmConsumer.Destroy();
This destroys the OmmConsumer event source, and in turn close all streams that were opened for the OMMConsumer.
- Session.Release();
This destroys the Session, and in turn destroy OMMComsumer which will close all streams.
I suggest using completion event to inform the application when the stream is closed and use this information to check what was happen at the time.
0 - UnregisterClient(itemHandle);
Answers
-
It may relate with parameter requestTimeout in RFA config. The default value is 45 sec. See RFA configuration section 3.1.1 RSSL Type Connection (RSSL Consumer).
Normally, RFA will generate the Timeout message once there is no response received for the item within a specific time. After that, RFA will re-request the item to recover data. The timeout can be configured by the requestTimeout configuration parameter ( 45 seconds by default).
It is possible that ADS you are connecting to, could not handle the number of requests that time. This issue should be verified by your market data engineer.
The RFA configuration may not relate with the close message you found. For testing purpose you may change it to 0 so the requests never timeout. Or you may change it to other value to see if you still get the close message in every 45 sec or not.
\Connections\Connection_RSSL\requestTimeout = 0
If the problem persists please open a new case to API support and provide full tracing log.
0 -
Its not timeout. We were getting market data for more than a day since the subscription was made. Better if your API team can look at the trace log. There are a large number of subscriptions . Consumer trace after zip is around 2GB and the publisher side trace is about a GB. How do we transfer this to you?
0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛