...
Active session was closed non-gracefully
Code Block language bash <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: This message appears when the session was terminated by Logout and IntradayLogoutTolerance mode is enabled. This mode means that during 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).
Troubleshooting steps: This doesn't indicate an issue, just informs that session was disconnected correctly and sequence numbers were preserved.
Reject task finished
Code Block language bash <Timestamp> INFO [Engine] Session <Session_Name> : Reject task finished.
Description: 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.
Troubleshooting steps: This doesn't indicate an issue, just informs that the task was finished.
The backup session has the same parameters as the primary session
Code Block language perl title FixEdge.log <Timestamp> INFO [Engine] Session <Session_Name> : The backlogbackup session has the same parameters as the primary session.
Description: This message appears when the backup session has the same parameters as the primary session.
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.
A FIX Session storage type isn't specified
Code Block language perl title FixEdge.log <Timestamp> INFO [Engine] <thread> Session property 'Session.TESTSESSION.StorageType' is not found. PersistentMM storage type is used.
Description: The option for storage type is not set so the most efficient storage type (PersistentMM) is used.
Troubleshooting steps: Make sure that the storage type is specified correctly. Check if there are spaces between the property and its value.