We use RFA.NET and LPC to get market price events stream. We have a wrapper application which uses RFA.NET and LPC to get market price events stream.
The application works by "Update" model which means we get connectivity status updates and market prices events via a queue.
In case we got login event with status other than OK, we are trying to reload our application (after recovery time threshold passed).
From time to time we have a connectivity issues like the below:
Login response: Data type : 141 Major version : 14 Minor version : 1 IsBlank : False HintMask : 2 IndicationMask : 0 MsgModelType : 1 MsgType : 1 RespType : Status RespTypeNum : 0 , Response status: StatusText : Force Logout from DACS. StatusTextW : StreamState : Closed DataState : Suspect StatusCode : 3 , Attributes: HintMask : 0 DataMask : 0 Name : NameType : 1 ServiceName : ServiceID : 0 ID : 0
When such event comes till now, we did the application reload as mentioned, but I'm wondering if this action is needed and if it can be helpful.
1. Do you have any built in mechanism which deals with connectivity issue, that knows how to recover/retry from the problematic state?
2. What's the recommended way to deal with connectivity issues when occur? Is any action needed?
3. By the way, does RFA.NET coupled to .NET framework yet?