...

This message occurs when there is an attempt to send a message to a not initialized ("logged in") Client of Transport Adapter (TA). The disclosed in log record "client" name represents the name of TA Client in FIXEdge.properties.

...

This is related to setup with LDAP authentication. Authentication is performed against Session identifier  (SenderCompID and TrargetCompID) and LDAP using the Username (tag 553) and Password (tag 554) from FIX Logon message.

...

1. Work with the counterparty to make sure that those supplied Logon credentials are correct.
2. Check if credentials are correct in LDAP and any other issues with LDAP itself.
3. Review and check the LDAPAuthenticate section in the BL_Config.xml file.
   

Unable to establish the connection (Error code = 10060)

<Timestamp>    ERROR    [Engine] <Thread ID>  Session <Session_Name> : Unable to establish connection: connect() to (xxx.xxx.xxx.x:xxxxx) failed. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (Error code = 10060)

...

1. Check what application uses the port. Make sure that another copy of the application is not running.
2. Modify the Listening ports in the engine.properties: ListenPort

DEBUG

...

Incorrect path to the properties file

<Timestamp>    DEBUGERROR    [BL_RoutingTableEngine] Unable  No OnActionFail is specified for rule for 'Rule_Name'

Description or root cause

...

to initialize EngineAdaptor. Reason: Please check settings: Cannot open the file "<path>". No such file or directory.

Description or root cause

This message appears when the IncludeProperties property is specified with the non-existent path. 

Solution or troubleshooting steps

This is not error, just indication that the <OnActionFail> condition might be also set up.

...

Change the value of the IncludeProperties property in the FIXEdge.properties file.

DEBUG

No OnActionFail is specified for the rule

<Timestamp>    DEBUG    [EngineBL_RoutingTable]  "StorageCreationTime" isNo updatedOnActionFail withis thespecified currentfor daterule in the FIX log storage "<path to file>/<storage file name with timestamp>", because of parameter absencefor 'Rule_Name'

Description or root cause

This

...

message

...

usually indicates that you have a routing rule, but haven’t specified what will happen if the Rule fails.

Solution or troubleshooting steps

This message can be ignored since it is not an error. 

WARN

...

error, just indication that the <OnActionFail> condition might be also set up.

'StorageCreationTime' property was updated

<Timestamp>    WARN DEBUG   [Engine]   Session <Session_Name> : the telecommunication link error was detected (Connection::receive(), EOF)"StorageCreationTime" is updated with the current date in the FIX log storage "<path to file>/<storage file name with timestamp>", because of parameter absence

Description or root cause

...

This message indicates that 'StorageCreationTime' property was updated in log storage. This message appears in case of re-using old FIX log storage with absent 'StorageCreationTime' property.

Solution or troubleshooting steps

Contact counter-party and query them for the sanity of their FIX adaptor/engine.

...

This message can be ignored since it is not an error. 

WARN

The telecommunication link error

<Timestamp>    WARN    [Engine]   Session <Session_Name> : FixEngine::CreateSession(...) "MessageStorageType storageType" parameter is deprecated. Please use SessionExtraParameters::storageType insteadthe telecommunication link error was detected (Connection::receive(), EOF)

Description or root cause

Some of the FIX Antenna API methods can become deprecated in the new version of the product's release. This message appears if the FIX Antenna API user creates the session with deprecated FixEngine::CreateSession API method and passes storage type not via SessionExtraParameters structure. It is recommended to pick another method for session creation.

Solution or troubleshooting steps

This message can be ignored. To remove this record from the log FIX Antenna user should use the non-deprecated FixEngine::CreateSession method.

The session was created in danger mode

...

It means that the TCP connection was terminated unexpectedly by the counter-party, without Logouts exchange.

Solution or troubleshooting steps

Contact counter-party and query them for the sanity of their FIX adaptor/engine.

"MessageStorageType storageType" parameter is deprecated

<Timestamp>    WARN    [Engine]  Session <Session_Name> : FixEngine::CreateSession(...) "MessageStorageType storageType" parameter is deprecated. Please use SessionExtraParameters::storageType instead

Description or root cause

Some of the FIX Antenna API methods can become deprecated in the new version of the product's release. This message appears if the FIX Antenna API user creates the session with deprecated FixEngine::CreateSession API method and passes storage type not via SessionExtraParameters structure. It is recommended to pick another method for session creation.

Solution or troubleshooting steps

This message can be ignored. To remove this record from the log FIX Antenna user should use the non-deprecated FixEngine::CreateSession method.

The session was created in danger mode

<Timestamp>    WARN    [Engine]  Session <Session_Name> : session was created in danger mode - it does not use persistent message storage

...

Make sure that the FIX message was re-transmitted correctly. If not, contact your counter-party counterparty regarding malformed messages from their side.

...

Parse Error : Incorrect size of a repeating group. Expected: 1. In fact: 2. Parsing stopped at column: 228 in tag N/A in message E with sequence number 979

...

This error will occur if the validation option 'verifyRepeatingGroupBounds' is enabled and FIX Engine receives a message with incorrect repeating group size. In this case, the FIX message will be rejected.

...

To revert this parameter after updating to the versions stated above, this parameter should be set to false. Additionally, for FIX Engine, the field should be set to false.

...

The authentication service doesn't send a response in time

<timestamp>   WARN    [LogonHandler]  <thread>  Session <SenderCompId, TargetCompId> : process logon failed  - request is timed out

...

Solution or troubleshooting steps

 Check the incoming FIX session logs and if there are no messages User Response (BF) then the issue is on the Authentification Service side.

INFO

...

FIXEdge can't create a log directory in the specified path

<Timestamp><timestamp>    INFOWARN    [Engine] Session <SenderCompId, TargetCompId>: There was an error while creating path <path>. Using default log directory <logDir>. SessionThe <Session_Name>error reason: <err.message>.

Description or root cause

This WARN record occurs if FIXEdge C++ can't create a log directory for the FIX session in the specified path.

Solution or troubleshooting steps

Check the value of the LogDirectory property specified for this session.

The property was overridden 

<timestamp>   WARN    [Engine] The "<property_name>"property was overridden by the file <filename>.

Description or root cause

This message appears when the value of some property was overridden by another properties file.

Solution or troubleshooting steps

This message can be ignored.

INFO

The active session was closed non-gracefully

<Timestamp>    INFO    [Engine]  Session <Session_Name> : Change state: old state=Established new state=NonGracefullyTerminated
<Timestamp>    INFO    [Engine]  Session <Session_Name> : active session was closed non-gracefully (The confirming Logout message was received from the counterparty.)

Description or root cause

...

 state: old state=Established new state=NonGracefullyTerminated
<Timestamp>    INFO    [Engine]  Session <Session_Name> : active session was closed non-gracefully (The confirming Logout message was received from the counterparty.)

Description or root cause

This message appears when the session was terminated by Logout and IntradayLogoutTolerance mode is enabled. This mode means that during the next session start the same set of logs will be used and the next Logon will be sent with sequence number previous+1 (unless you use ForceSeqNumReset=ALWAYS. See matrix of possible IntradayLogoutTolerance+ForceSeqNumReset combinations).

Solution or troubleshooting steps

This message doesn't indicate an issue, just informs that session was disconnected correctly and sequence numbers were preserved.

Reject task finished

<Timestamp>    INFO    [Engine]  Session <Session_Name> : Reject task finished

Description or root cause

 In FIXEdge there is an option to reject messages that should be routed into the session, which exists, but currently isn't available. This message appears when all such messages were rejected.

Solution or troubleshooting steps

This message doesn't indicate an issue, just informs that session was disconnected correctly and sequence numbers were preserved.

...

the task was finished.

The backup session has the same parameters as the primary session

<Timestamp>    INFO    [Engine]  Session <Session_Name> : Reject task finished

Description or root cause

...

 The backup session has the same parameters as the primary session

Description or root cause

This message appears when the backup session has the same parameters as the primary session.

Solution or troubleshooting steps

This message doesn't indicate an issue, just informs that the task was finished.

...

backup session

...

's parameters are the same as for the primary session.

A FIX Session storage type isn't specified

<Timestamp>    INFO    [Engine]  <thread> Session <Session_Name> : The backup session has the same parameters as the primary sessionproperty 'Session.TESTSESSION.StorageType' is not found. PersistentMM storage type is used

Description or root cause

This message appears when the backup session has the same parameters as the primary sessionThe option for storage type is not set so the most efficient storage type (PersistentMM) is used.

Solution or troubleshooting steps

This message doesn't indicate an issue, just informs that the backup session's parameters are the same as for the primary session.

...

Make sure that the storage type is specified correctly. Check if there are spaces between the property and its value.

New log message storage was created

<Timestamp>   INFO    [Engine]  <thread> Session <sender, property 'Session.TESTSESSION.StorageType' is not found. PersistentMM storage type is usedtarget> : Created new [FIX/FAST] log storage with file name "<path to file>/<storage file name with timestamp>"

Description or root cause

The option for storage type is not set so the most efficient storage type (PersistentMM) is usedThis message appears when FIX Antenna creates new log message storage.

Solution or troubleshooting steps

Make sure that the storage type is specified correctly. Check if there are spaces between the property and its value.

...

This message doesn't indicate an issue, just informs that the task was finished.

LogDirectory property was specified with a non-existent path

<Timestamp>   INFO    [Engine]  <thread> Session <sender, target> : CreatedPath new [FIX/FAST] log storage with file name "<path to file>/<storage file name with timestamp>"<location> doesn't exist. Trying to create it.

Description or root cause

This message appears when FIX Antenna creates new log message storage message appears when the LogDirectory property was specified with the non-existent path for the FIX session.

Solution or troubleshooting steps

This message doesn't indicate an issue, just informs that the task was finished can be ignored. To use the particular existing log directory user must change the value of the LogDirectory property for the FIX session.