Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Description or root cause

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

Solution or troubleshooting steps

These are This is not errorserror, just indications indication that the <OnActionFail> condition might be also set up.

WARN

...

'StorageCreationTime' property was updated

Code Block
languagebash
<Timestamp>    WARN DEBUG   [Engine]  "StorageCreationTime" Sessionis <Session_Name>updated :with the telecommunication link error was detected (Connection::receive(), EOF)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.

"MessageStorageType storageType" parameter is deprecated

...

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

WARN

The telecommunication link error

Code Block
languagebash
<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

Code Block
languagebash
<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

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

...

 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

The active session was closed non-gracefully

Code Block
titlelanguageengine.logbash
<Timestamp>    WARNINFO    [Engine]  Session <thread><Session_Name> Cannot: findChange thestate: property "StorageCreationTime" in the storage "<path>/<session id>_<timestamp>", used current date.

Description or root cause

...

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

 Ignore, if starting a session without any previous state (For example on the clean log)

INFO

The active session was closed non-gracefully

...

languagebash

...

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

Reject task finished

Code Block
languagebash
<Timestamp>    INFO    [Engine]  Session <Session_Name> : active session was closed non-gracefully (The confirming Logout message was received from the counterparty.)Reject task finished

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) 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

Code Block
bash
languageperl
titleFixEdge.log
<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 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

Code Block
languageperl
titleFixEdge.log
<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

Code Block
languageperl
titleFixEdge.log
<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 valueThis message doesn't indicate an issue, just informs that the task was finished.