• Programming Guide
  • Api Documentation
  • OnixS CME iLink3 Handler for .NET Core, version 1.4.2
Show / Hide Table of Contents
  • Introduction
  • System Requirements
  • Getting Started
    • Error Reporting
    • Licensing
    • SBE Message
      • Tag-based Messaging
      • Message Fields
      • Repeating Groups
    • iLink 3 Session
      • Universally Unique Identifier
      • Establishing iLink3 Connection
      • Exchanging Messages
      • Message Sequence Numbers
  • Configuring the Handler
    • Configuration File Examples (XML or JSON)
  • Logging
  • Session Storage
    • File-Based Session Storage
    • Memory-based Session Storage
    • Asynchronous File-Based Session Storage
    • Pluggable Session Storage
  • Advanced Programming
    • Thread Safety
    • Session Initialization and Binding
    • Session States
    • Listening to Session Events
    • Handling NotApplied Messages
    • Handling Business Reject Messages
    • Automated Downloading of GTC and GTD Orders
    • Reconnection
    • Fault Tolerance
    • Understanding Send Latency
    • Strongly Typed Messages
  • Best Practices
    • Low Latency Best Practices
  • Glossary
  • Support

Message Sequence Numbers

Message Sequencing

Each FIXP Protocol Session establishes independent incoming and outgoing message sequence numbers series.

Sequence numbers are initialized at the start of an iLink 3 logical session, starting at 1 and incremented by each application-level message through the session.

A single iLink 3 logical session with the same Universally Unique Identifier can exist across multiple sequential physical connections. The client can connect and disconnect multiple times while maintaining the same iLink 3 logical session.

Once the Disconnect(Boolean) method is called, the physical connection is terminated, but the logical session does not end its lifetime. It is possible to continue the session later, using the Connect(String, Int32) method again.

fixp session sequence numbers

See Also

Restoring Session State

Manipulating Message Sequence Numbers

To get the expected sequence number of the next incoming message, use the InSeqNum property.

To get the sequence number of the next outgoing message, use the OutSeqNum property.

Resetting Sequence Numbers

Resetting inbound and outbound message sequence numbers back to 1, for whatever reason, constitutes the beginning of a new logical iLink 3 session that should have a new UUID. The Reset(Boolean) method must be used to back up previous log files, generate a new UUID, and reset sequence numbers to 1.

Note

InSeqNum and OutSeqNum methods can be used to set expected sequence numbers manually before an iLink 3 connection is established. However, it is NOT recommended to use these methods to reset the message sequence numbers back to 1 to start a new logical iLink 3 session. Instead, use the Reset(Boolean) method.

In This Article
Back to top Copyright © Onix Solutions.
Generated by DocFX