• Programmer’s Guide
  • Api Documentation
  • Recovery
Show / Hide Table of Contents
  • License Agreement
  • Release Notes
  • Backgrounder
    • About FIX
    • About FIX messages
    • About FIX sessions
    • About FIX 5.0
  • Installation And Uninstallation
    • Requirements & Compatibility
    • Supported Features
    • Samples descriptions
    • Uninstallation instructions
  • Quick Start
    • Session acceptor creation
    • Session initiator creation
    • Creating new order
    • Sending order
    • Processing incoming message
    • Closing session
    • Sample application
  • Basic Concepts
    • Main components
    • FixServer description
    • IFixServerListener description
    • IFixSessionListener description
    • IFixSession description
    • Repeating Groups description
    • Message validation
  • FIX Session Acceptor
    • Create
    • Connect
    • Reject
    • Reconnect
    • Disconnect
    • Release
    • Send message
  • FIX Session Initiator
    • Create
    • Establish connection
    • Reconnect
    • Disconnect
    • Dispose
    • Send message
  • FIX Session
    • Persistent session
    • Session state
    • Sequence number handling
    • Session qualifier
  • FIX Message
    • Create
    • Get field
    • Add field
    • Set field
    • Remove field
    • Repeating group
    • User defined fields
    • Clone message
  • FIX Prepared Message
    • Create
    • Add field
    • Set field
  • Repeating Group API
    • Indexing Repeating Group
    • Working with Repeating Groups through API
    • Repeating Group Pool
    • Get Repeating Group
    • Get Entry
    • Get nested group
    • Add new Repeating Group to message
    • Add new Entry to Repeating Group
    • Remove Entry from Repeating Group
    • Leading tag self-maintaining
    • ITagList interface
    • Validation
    • Copying
    • Finishing work with Repeating Group API
  • Validation
    • Initialization
    • Validation
  • Monitoring and Administration
    • Overview
    • Response result codes
    • Supported commands
  • Recovery
    • Store-and-forward
    • Gap fill
    • Fail-over
  • Configuration
    • Global configuration
    • Server Behavior
    • Queue and Storage
    • Validation
    • Administrative plugin
    • Session’s configuration
    • Configure SeqNum fields length
    • Definition of session’s configuration via properties file
    • Definition of session’s configuration via XML file
    • Loading of session’s configuration
  • TLS Support
    • SSL/TLS configuration
    • How to define an SSL certificate
    • How to use sslPort and requireSsl configuration options
    • Configuration examples
    • Diagnostic and troubleshooting
  • Other Topics
    • Log files
    • FAQ
    • Troubleshooting

Recovery

Store-and-forward

FIX Antenna follows two main rules:

  1. An outgoing message is saved to the file and then sent
  2. An incoming message is saved to the file after it is processed

There are two very important consequences of these rules that in combination with FIX sequencing and retransmission make losing a message in FIX Antenna impossible:

  1. If application crashes during the incoming message processing, it will not be stored, hence after restoring a session the sequence number too high will be identified and resend request will be sent.
  2. If application crashes before a message is delivered to a counter-party, the counter-party will identify a gap and send a request for retransmission after restoring a session.

Gap fill

Gap fill is a standard FIX mechanism designed to indentify and resolve message loss. It is based on sequencing messages in each direction, resend request mechanism, PosDup flag and sequence reset.

When session identifies the sequence number too high problem it sends a resend request message asking for retransmission of lost messages. The opposite side resends requested messages with PosDupFlag set to Y. Session level messages are not resent. The sequence reset is used to keep sequence numbers consistent during resending.

FIX Antnenna automatically resolves gap fill, i.e. no manual work is required. However it is possible to intervernt into standard mechanism.

Fail-over

FIX Antenna comes with a basic failover mechanism. If application crashes after the next initialization FIX Antenna will fully restore its state as it was before the crash. No information will be lost.

In This Article
  • Store-and-forward
  • Gap fill
  • Fail-over
Back to top Generated by DocFX