Warning :RSSL Connection "received message for a not registered item"
I am hoping some of the experts here can shed some light on a warning message: Developer is seeing several of the following Warning message in his log file for the same stream;
11:57:09.869304 INF RDM/RDMClient.cpp(200)[0x7fd7877fe700] LoggerNotifyEvent from RSSL_Cons_Adapter2[Mon Jan 13 11:57:09 2014]: (ComponentName) RSSL_Cons_Adapter: (Severity) Warning: "Connection_RSSL" received message for a not registere d item: stream id = 204
11:57:09.869383 INF RDM/RDMClient.cpp(200)[0x7fd8127fc700] LoggerNotifyEvent from RSSL_Cons_Adapter2[Mon Jan 13 11:57:09 2014]: (ComponentName) RSSL_Cons_Adapter: (Severity) Warning: "Connection_RSSL" received message for a not registere d item: stream id = 204
followed by disconnect from the ADS.
11:57:09.940594 INF RDM/RDMClient.cpp(200)[0x7fd7877fe700] LoggerNotifyEvent from RSSL_Adapter1[Mon Jan 13 11:57:09 2014]: (ComponentName) RSSL_Adapter: (Severity) Information: RSSL Channel closing on connection "Default::Connection_RSSL p2psa.eur.nsroot.net:14002" due to "requested disconnect"
Has anyone come across the above warnings? Under what circumstances could a consumer client receive events for an unregistered item?
Best Answer
-
Client may see this warning message when the consumer application received message (e.g. Update, Refresh) that is unexpected by the consuming application. Often, the common case for this is when the consumer receives Update/Refresh of the item that RFA has already unregistered the handle of that item.
When client requests to close/unregister the handle, RFA internally send Close Message to the provider. There can be some delay while the Close Message is being transported to the provider. During this delay period, the provider may still send down response messages( e.g. Update message) to the consumer, if this happens , RFA consumer will process these messages, but it could not match these messages to any opening stream ( due to the stream is closed by RFA , and removed from its watch list). Therefore, RFA will generate this warning message and log through RFA Logger ,and won’t forward the response messages to the application. As the matter of fact, the warning message is harmless.
0
Categories
- All Categories
- 6 AHS
- 37 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
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛