• 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

Reconnection

When the session is in the active state, and there are some network issues, the Handler will try to restore the connection per ReconnectAttempts and ReconnectInterval settings.

When a network error is detected, the session changes its state to Reconnecting and tries to re-establish the connection ReconnectAttempts times with the ReconnectInterval delays between attempts.

  • If the connection is restored, the session changes its state to Established.
  • If the connection cannot be restored automatically, the session changes its state to Disconnected. After that, the connection attempt could be repeated "manually" using the Connect(String, Int32) method.
Note

Reconnection works for established iLink 3 connections only.

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