|
OnixS C++ FIX Engine
|
2.79.1.0
|
- Q: I need to continue the FIX session starting from the specific message sequence number, but I have deleted the log files from the previous runs. How can I do this?
- A: You can use OnixS::FIX::Session::setInSeqNum and OnixS::FIX::Session::setOutSeqNum members to set the start sequence numbers before establishing the session. For more information, take a look at Message Sequence Numbers topic.
- Q: How can I customize OnixS C++ FIX Engine to work with non-standard FIX counterparties that employ user-defined fields and messages (use modifications of the FIX Protocol)?
- A: You should define and use the corresponding XML-based FIX Dialect description. For for information, take a look at FIX Dialects topic.
- Q: What is the default behavior of the OnixS C++ FIX Engine in case a Test Request <1> message was sent to the counterparty and the counterparty does not respond?
- A: When the response on the Test Request <1> message is not received during HeartBeatInt, the FIX Connection is considered lost. Session-acceptor changes its state to OnixS::FIX::Session::LOGON_IN_PROGRESS in such case. Session-initiator changes its state to OnixS::FIX::Session::RECONNECTING and tries to restore the FIX Connection pre-configured number of times in pre-configured interval (using the binary exponential back off algorithm). Please note that FIX Engine automatically handles sending of Test Request messages (when needed). For more information, take a look at Complete Reference of Configuration Settings topic.
- A: Take a look at Connecting using Custom Logon Message topic.
- Q: Why do I receive the "Invalid FIX Engine settings: Cannot open the persistent
storage folder ('MsgStorage')" error when I'm trying to run my FIX application as a Windows service? When I run my application as a standalone one, all work perfectly OK.
- A: The reason of this error is the different default current folder for Windows Service and Windows application. By default, the current directory for your Windows service is the System32 folder. To solve this issue specify the full path to the persistent storage folder using the Log.Directory setting.
- A: You can use OnixS::FIX::Session::senderSubID, OnixS::FIX::Session::targetSubID, OnixS::FIX::Session::senderLocationID, OnixS::FIX::Session::targetLocationID methods of the OnixS::FIX::Session class.
- Q: How will I know if I do not have the valid license file? What is a failure scenario/message for the Engine?
- A: When the license expires OnixS::FIX::EngineException is thrown during the call of the OnixS::FIX::Engine::Init method. For more information read Licensing topic.
- Q: Is there any way to check whether Logon and/or Logout messages are received?
- A: Yes. Override OnixS::FIX::ISessionListener::onInboundSessionMsg virtual member and you'll be able to check all session-level messages including Logon and Logout.