RSSL Adapter Error 10121
Hello,
We had process hung for a few time in the past month and we suspected that the Adapter thread had issues. Please see the below RFA log. The last seen logging line of our handler was 11/23 19:00:31.250436, EST. We're using RFA C++ API 8.1.x. The application uses notification client model, and the threadModel is not set (so default to Dual). Could you please check and let's know the meanings of the error code, plus the reason for this if possible?
[Mon Nov 23 19:00:00 2020]: (ComponentName) RSSL_Adapter: (Severity) Error: 10121 (Default::Connection_RSSL 10.200.105.202:14002)
Thanks,
[Mon Nov 23 14:00:02 2020]: (ComponentName) RSSL_Cons_Adapter: (Severity) Information: 6000 (Default::RSSL_Cons_Adapter) [Mon Nov 23 14:00:02 2020]: (ComponentName) RSSL_Cons_Adapter: (Severity) Information: 6001 () [Mon Nov 23 14:00:02 2020]: (ComponentName) RSSL_Cons_Adapter: (Severity) Information: 6032 (Default::Connection_RSSL) [Mon Nov 23 14:00:02 2020]: (ComponentName) RSSL_Cons_Adapter: (Severity) Warning: 6034 (Default::Connection_RSSL 10.200.105.202:14002) [Mon Nov 23 14:00:02 2020]: (ComponentName) RSSL_Cons_Adapter: (Severity) Information: 6010 (Default::Connection_RSSL 10.200.105.202:14002) [Mon Nov 23 14:00:02 2020]: (ComponentName) RSSL_Adapter: (Severity) Information: 10125 (Default::Connection_RSSL 10.200.105.202:14002) [Mon Nov 23 14:00:02 2020]: (ComponentName) RSSL_Adapter: (Severity) Information: 10102 (Default::Connection_RSSL 10.200.105.202:14002) [Mon Nov 23 14:00:02 2020]: (ComponentName) RSSL_Adapter: (Severity) Information: 10134 (Requested version: 14.1, Connected version: 14.1) [Mon Nov 23 14:00:02 2020]: (ComponentName) RSSL_Adapter: (Severity) Information: 10104 (Default::Connection_RSSL 10.200.105.202:14002) [Mon Nov 23 14:00:02 2020]: (ComponentName) RSSL_Cons_Adapter: (Severity) Information: 6015 (Default::Connection_RSSL 10.200.105.202:14002) [Mon Nov 23 14:00:02 2020]: (ComponentName) SessionCore: (Severity) Warning: 1015 (Connection_RSSL) [Mon Nov 23 14:00:02 2020]: (ComponentName) SessionCore: (Severity) Warning: 1016 (Connection_RSSL) [Mon Nov 23 19:00:00 2020]: (ComponentName) RSSL_Adapter: (Severity) Error: 10121 (Default::Connection_RSSL 10.200.105.202:14002) [Mon Nov 23 19:00:04 2020]: (ComponentName) RSSL_Adapter: (Severity) Warning: 10105 (Default::Connection_RSSL 10.200.105.202:14002) [Mon Nov 23 19:00:04 2020]: (ComponentName) RSSL_Cons_Adapter: (Severity) Information: 6015 (Default::Connection_RSSL 10.200.105.202:14002) [Mon Nov 23 19:00:04 2020]: (ComponentName) RSSL_Cons_Adapter: (Severity) Information: 6011 (Default::Connection_RSSL 10.200.105.202:14002) [Mon Nov 23 19:00:25 2020]: (ComponentName) RSSL_Adapter: (Severity) Information: 10125 (Default::Connection_RSSL 10.200.105.202:14002) [Mon Nov 23 19:00:25 2020]: (ComponentName) RSSL_Adapter: (Severity) Information: 10102 (Default::Connection_RSSL 10.200.105.202:14002) [Mon Nov 23 19:00:25 2020]: (ComponentName) RSSL_Adapter: (Severity) Information: 10134 (Requested version: 14.1, Connected version: 14.1) [Mon Nov 23 19:00:25 2020]: (ComponentName) RSSL_Adapter: (Severity) Information: 10104 (Default::Connection_RSSL 10.200.105.202:14002) [Mon Nov 23 19:00:25 2020]: (ComponentName) RSSL_Cons_Adapter: (Severity) Information: 6015 (Default::Connection_RSSL 10.200.105.202:14002) [Mon Nov 23 19:00:25 2020]: (ComponentName) SessionCore: (Severity) Warning: 1015 (Connection_RSSL) [Mon Nov 23 19:00:25 2020]: (ComponentName) SessionCore: (Severity) Warning: 1016 (Connection_RSSL)
Kind Regards,
Refinitiv
Best Answer
-
It looks like you did not deploy the message file in the running directory, so it does not show the logger details.
I check the message id from file RFA8_RSSL_Adapter.mc provided under folder <RFA SDK Path>/MessageFiles, and it seems to be the following message.
MessageId=10121
Severity=Error
Facility=Application
SymbolicName=RSSL_CHANNEL_READ_FAILED
Language=English
RSSL Channel read failed on connection "%1". Channel will be closed. (Internal debug info: "%2", errno: %3)It should be the case that RFA unable to connect to server 10.200.105.202 using the RSSL connection port. App side should receive the connection down, and you might need to verify the connection to the server.
0
Answers
-
did it mean that the adapter could not connect to the TREP server on that port? what was the reason it failed to connect?
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 687 Datastream
- 1.4K DSS
- 621 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 254 ETA
- 557 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 276 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 669 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 193 TREP Infrastructure
- 229 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛