Page tree
Skip to end of metadata
Go to start of metadata

FIXEdge/J 1.5.1

June 1, 2020

New Features and Improvements

  • Improved support for FIX Integrated Control Center.
    • FIX Integrated Control Center is able to monitor and manage FIX sessions (including scheduled ones) and can reload updated session configurations without restarting FIX Edge Java. Please see more.
  • SMTP endpoint is implemented.
    • SMTP endpoint allows routing of FIX messages and systems events (like FIX session connect/disconnect events) to emails. Please see the documentation about SMTP Endpoint here.

Bugs and fixes

  • Kafka Endpoint can't publish/consume messages in a custom format. 
    • Problem description:  serializer/deserializer classes were hardcoded to work with FIX messages in key-value string format. 
    • Solution: Hardcode was removed and new interfaces for serialization/deserialization of MessageEvent instance into custom format were provided.
  • The scheduler doesn't start the session in the middle of the day.
    • Problem description:  FIX session does not start if FEJ server has started after its start time but before its stop time.
    • Solution: The scheduler logic was fixed and now it can start FIX sessions if the FEJ is started during their working hours.


FIXEdge/J 1.4.1

March 6, 2020

Bugs and fixes

  • Kafka Endpoint can't be started by the scheduler. 
    • Problem description: All Kafka Endpoints are started right after the initialization and it's impossible to manage them later by the scheduler tasks.
    • Solution: The flexibility of initialization for Kafka Endpoints was enhanced.

FIXEdge/J 1.4.0

April 3, 2019

New Features and Improvements

  • Event API extension was added.
    • Added the ability to pass and handle different types of events from endpoints and scheduler in groovy routing rules (handle FIX session connect/disconnect, for example).
  • Integration with Apache Kafka streaming platform.
    • Kafka Endpoint implementation is based on FIX Antenna Java Kafka Adapter and uses internally Kafka Producer and Consumer API.
  • Integration with Apache Camel.
    • Camel Endpoint is added into FIXEdge Java as a destination endpoint which allows publishing the messages to the wide range of its connectors.
  • Scheduler functionality was enhanced.
  • Username/password validation is enabled for FIX sessions.
    • Username and password properties may be defined in FIX session configuration to send them to the counterparty or to authorize the client.
  • Custom FIX dictionaries for FIX sessions.
    • Custom dictionaries with their own IDs for FIX sessions can be defined in the configuration now. Read more.
  • JMX controls for Kafka and JMS endpoints were added.
  • Store And Forward logic can be used within a cluster.
    • REPLICATED persistence mode was added to support the replication of queued messages to backup nodes.
  • New options to control Store And Forward queues.
    • Added new options maxNumberOfMessagesInMemory and maxQueueWaitingTimeInMsec for Store And Forward queue.
  • Strategy for automatic leader election was implemented.
    • The logic for election the next leader node was moved to a separate interface. It is accessible for implementation. Also a new strategy with the prioritized list of nodes was provided(TODO:link to strategy and description)
  • Automatic reelection of a leader in the cluster.
    • Implemented an ability to automatically choose a new leader if the previous was disappeared. This feature is disabled by default.
  • Measure routing performance benchmark sample was added.
    • Find a source code of sample in benchmarks directory.
  • Spring Security 5.2 update
    • Authorization for administrative connections gets more configuration options with Spring Security 5.2
  • FIX Antenna Java 2.21.1 update.

Bugs and fixes

  • The invalid stale period calculation for messages in Store and Forward queue. 
    • Problem description: Stale period for messages in Store and Forward queue (storeAndForward.stalePeriod option) worked differently in different time zones. 
    • Solution: a strategy for managing 'stale' messages was fixed.
  • FIX session disappears right after disconnect.
    • Problem description: disposeOnDisconnect option was active by default and FIX sessions are destroyed in case of any disconnect  (due to network problems for example).
    • Solution: option is disabled in default FIX session configuration.
  • Reconnecting FIX session doesn't stop when the cluster node is switched to backup mode.
    • Problem description: When a new leader is elected in the cluster, initiator sessions, which are trying to reconnect on previous leader node, aren't stopped. As a result, it may lead to restoring FIX connection with the wrong node.
    • Solution: All sessions are disposed when the cluster node role switches from leader to backup.
  • FIX Endpoint may send a Heartbeat(0) message before Logon(A) on connect.
    • Problem description: There was a bug in FIX Antenna Java and it may send a Heartbeat(0) message before Logon(A) for a new FIX session.
    • Solution: FIX Antenna Java updated to version 2.21.1, which includes fix for sync_noqueue mode.

FIXEdge/J 1.3.0

April 3, 2019

New Features and Improvements

  • Added key-value in-memory data storage.
    •  FIXEdge/J provides an ability to store information in the memory for purposes of message enrichment during the routing process. Please find additional information in the article In-memory data context.
  • Added Store-And-Forward intermediate queue.
    • FIXEdge/J provides functionality that messages are stored and forwarded in the event that a connection with one of the counterparties is dropped and messages are not delivered. For additional information please refer to the article Store And Forward Queue.
  • Configuration and deployment to WildFly were added.
    • Added ability to deploy and configure FIXEdge/J on a Wildfly server. For additional information please refer to the article Installation in WildFly
  • Added support for session qualifiers.
    • Session qualifier gives the user an ability to create several sessions with the same SenderCompId and TargetCompId.
  • FIXEdge/J 1.3.0 is based on the FIX Antenna Java 2.20.0.

Bugs and fixes

  • FIXEdge/J does not log the session initialization/registration event.
    • Problem description: FIXEdge/J creates/registers/initializes session according to the schedule. The record about this event doesn't appear in the log.
    • Solution: Logging process of such events was fixed.
  • No labels