FIX Antenna HFT 1.0.11 Release Notes
FIX Antenna HFT 1.0.11 released on 13 April, 2018
New Features and Improvements:
- Search in the FIX Antenna HFT Programmer's Guide has been added
The following bugs have been fixed:
- Failures on flushing session log cache leads to FIX Engine termination
- Session picks up logs of previous year instead of the latest logs from the log directory
- EchoServer sample: engine.log contains messages without logging level and spaces
FIX Antenna HFT 1.0.10 Release Notes
New Features and Improvements
- Allowed to pause/resume session socket reading to prevent overload on application side, see “Router” sample for more details.
- Introduced a new callback Engine::Application::onSessionLevelRejectEvent used for passing FIXMessageProcessElem flags toLiteFixMessage Rejects (35=3) , see "Router" sample for more details.
- Added error message in the log file for the case when PossDupFlag(43) is required but absent in the incoming message.
Critical bugs and fixes
The following bugs have been fixed:
- Session onLogout callback is called twice in some cases
- Timer thread sometimes doesn't call ThreadsPool::Listener::onNewThreadCreated() (callback that allows user to setup thread affinity)
- canThrottle flag is always set to “false”
FIX Antenna HFT 1.0.8 Release Notes
FIX Antenna HFT 1.0.8 released on 28 July, 2017
New Features and Improvements
- OpenSSL symbols have been hidden to avoid compatibility issues
Critical bugs and fixes
The following bugs have been fixed:
- TCP reader stops reading in some cases on receiving new connection
- Milliseconds are truncated after serialization for fields with types UTCTimestamp and UTCTimeOnly when milliseconds value is 000
FIX Antenna HFT 1.0.7 Release Notes
FIX Antenna HFT 1.0.7 released on April 4, 2017
New Features and Improvements
- The "Router sample" has been added to the package
- Some API functions/parameters have been documented
Critical bugs and fixes
The following bugs have been fixed:
- Processing of garbled messages is incorrect
- Tag 122 in Sequence Reset (4) message should be same as tag 52 (including milliseconds)
- Session is hanging on receiving non-valid Logon message