OnixS C++ FIX Engine  4.6.0
API Documentation
ExternalThread Mode

Sometimes, it is more effective to perform the event dispatching in a loop in the main application thread. For this purpose, one can use the OnixS::FIX::ThreadingModel::ExternalThread mode.

The OnixS::FIX::ThreadingModel::ExternalThread mode is supported for initiator sessions only.


Before an externally-managed session is created, the application must create an OnixS::FIX::ISessionReactor instance. There are two reactor classes, which can be used:

TCPStandard::Stack stack;

The pointer to the stack is provided in Session's constructor, for example:

SessionListener listener;
Session session(&stack, SenderCompId, TargetCompId, FixProtocolVersion, &listener);

Asynchronous Logon and Logout

Applications must call asynchronous Session's methods to logon (OnixS::FIX::Session::logonAsInitiatorAsync) and logout (OnixS::FIX::Session::logoutAsync).

session.logonAsInitiatorAsync(counterpartyHost, counterpartyPort, heartBtInt, ONIXS_FIXENGINE_NULLPTR, true);
// Dispatching events..
session.logoutAsync("End of connection");

Dispatching Network Events

Applications must call OnixS::FIX::TCPStandard::Stack::dispatchEvents frequently for each stack that is in use.

bool finished = false;
while (!finished)


The TCPStandard stack requires finishing all outstanding work and handling all outstanding events. Before destroying the OnixS::FIX::TCPStandard::Stack instance, the following code should be executed:

while (!stack.isQuiescent())

Method OnixS::FIX::TCPStandard::Stack::isQuiescent returns a boolean value indicating whether a stack is quiescent.

This can be used to ensure that all connections have been closed gracefully before destroying a stack (or exiting the application). Destroying a stack while it is not quiescent is permitted by the API, but when doing so there is no guarantee that sent data has been acknowledged by the peer or even transmitted, and there is the possibility that peers' connections will be reset.

See Also