FIX Antenna HFT Release Notes
- 1 FIX Antenna HFT 1.0.18 - Release Notes
- 2 FIX Antenna HFT 1.0.17 - Release Notes
- 3 FIX Antenna HFT 1.0.16 - Release Notes
- 4 FIX Antenna HFT 1.0.14 - FA 2.9.53 Release Notes
- 5 FIX Antenna HFT 1.0.13 - FA 2.9.51 Release Notes
- 6 FIX Antenna HFT 1.0.11 Release Notes
- 7 FIX Antenna HFT 1.0.10 Release Notes
- 8 FIX Antenna HFT 1.0.8 Release Notes
- 9 FIX Antenna HFT 1.0.7 Release Notes
FIX Antenna HFT 1.0.18 - Release Notes
FIX Antenna HFT 1.0.18 is released on Jan 20, 2026
New Features and Improvements
iLink3:
Update CME iLink3 schema to version 9.
Added SessionReset command to certification tool in order to clean session start without application restart.
Audit trail tool is updated to strictly conform to CME specification.
FIX Antenna HFT 1.0.17 - Release Notes
FIX Antenna HFT 1.0.17 is released on Feb 14, 2025
New Features and Improvements
B3 Exchange Connectivity and Tools:
B3 SBE Order Entry Adapter: Introduced to provide direct, high-performance connectivity to the B3 exchange using the efficient SBE protocol, expanding market reach for users.
B3 Binary Log Converter: Implemented to simplify the analysis of B3 binary logs, aiding in debugging, performance analysis, and monitoring of market activity.
Performance Optimization:
Message Batch Sending Functionality: This feature ensures that related messages, such as those for orders belonging to a specific strategy, are delivered to an exchange with minimal delay between the messages, essentially simultaneously.
Fixed Bugs
Crash Fix for Null Storage Initiator Sessions: Addressed a critical application crash occurring when null storage was used in initiator sessions, improving session management reliability.
Codebase and Maintainability Improvements
iLink3 Parser Generator Modernization: Updated the iLink3 parser generator to a more modern codebase, setting the stage for improved code generation and future enhancements in iLink3 support.
FIX Antenna HFT 1.0.16 - Release Notes
FIX Antenna HFT 1.0.16 is released on 27th of February 2024
New Features and Improvements
A new audit trail tool has been introduced to satisfy the requirements for CME iLink 3 certification.
LiteFixMessage now allows for tags with numbers higher than 65535.
The logs converter tool has been updated to support CME MDP 3 and BrokerTec protocols.
Users can now substitute the default iLink 3 binary parser with a custom parser implementation.
FIX Antenna HFT can now handle several FIX sessions with the same SenderCompID and TargetCompID by using the FIXCompIdCutoffMarker property.
Added ability to set iLink 3 SendingTimeEpoch automatically for the messages that support it.
Introduced the ability to measure latency before data is sent through the socket and comprehensive measurement of full processing latency while sending.
Critical bugs and fixes:
FIX Antenna HFT has been fixed to allow for the establishment of a FIX session when connected to CME BrokerTec.
A segmentation fault caused by the UseTCPDispatcher property being set to 'true' and receiving incomplete initial FIX message data is now resolved.
The iLink3_logs_converter now correctly populates audit fields (6, 28) for Order Cancel or Cancel Replace Reject messages.
FIX Antenna HFT 1.0.14 - FA 2.9.53 Release Notes
FIX Antenna HFT 1.0.14 based on FIX Antenna 2.9.53.276 released on 28th of April 2021
New Features and Improvements
Added support of iLink3 binary protocol v7. Details can be found at iLink3 support guide page .
Added iLink3 binary logs to FIX/ HumanReadable converter available as sample.
Added CME Audit Trail report generation tool available as sample.
FIX Antenna HFT 1.0.13 - FA 2.9.51 Release Notes
FIX Antenna HFT 1.0.13 based on FIX Antenna 2.9.51.213 released on 3rd of April 2019
Breaking changes:
Library for platform RHEL 6 using C++ 98 ABI is deprecated and will be removed from the package starting next release
Restored FIX-Protocol compatibility when a session is terminated if re-transmitted GapFill (35=4) message does not have PossDup flag (43=Y).
The previous behavior can be enabled with the following configuration set:engine.properties
AllowMessageWithoutPossDupFlag = true AllowGapFillWithoutPossDupFlag = trueRejected messages are not filtered out and replaced with gap-fill messages in resend request replies.
Changed naming convention libV12-gcc63-MD-x64.so → libV12-gcc52-MD-x64.so.
The libraries libV12-gcc48-MD-x64.so and libV12-gcc44-MD-x64.so are considered as depreciated. Support C98 Standard and Red Hat 6 platform will be discontinued in one of the next releases.
(SD4906754) Engine::SessionsManager::onIncomingConnection callback API has been extended with delivering the port number for accepted connection.
New Features and Improvements
Added a new session property AllowGapFillWithoutPossDupFlag to support some exchanges that stepping aside from FIX protocol restrictions and sending GapFill (35=4) messages without PossDup flag (43=Y) and avoid such sessions termination.
Add smart delay balancing logic to avoid wrong unsuccessful attempts of system calls to map cache of persistentCached storage type in case of very large log files being opened simultaneously.
Speedup detection of corrupted storages
(SD4906754) Added public API methods: FAProperties::getListenPorts(), FixEngine::getListenPorts() which returning a list of ports for acceptors.
(SD4906754) Added public API methods: FAProperties::getNonAccelListenPorts(), FixEngine::getNonAccelListenPorts() which returning a list of ports for acceptors using non-accelerated dispatcher.
Critical bugs and fixes:
(SD4998782) Fixed a bug when the engine can try to close random file descriptors at destroying.
Fixed a bug when the engine stops sending heartbeats to all sessions if one session is locked e.g. due to long processing of the resend request message.
Fixed a bug when any resend requests processing takes too much time (several seconds) on the large FIX-messages storages (about 10 GB).
Logging improvements:
(SD4906754) A log record about incoming connection event has been extended with ip and port that have accepted the connection
Known issues
New Incoming connection event is raised on any small amount of received data (e.g. even 1 byte)
OpenOnload accelerated dispatcher and standard dispatcher act differently if an incoming invalid message has sequence lower than expected. Standard dispatcher disconnects sessions according to FIX-protocol recommendations but OpenOnload accelerated dispatcher keeps the session alive.