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
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.
