...
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.
...
- Work with the counterparty to make sure that those supplied Logon credentials are correct.
- Check if credentials are correct in LDAP and any other issues with LDAP itself.
- Review and check the LDAPAuthenticate section in the BL_Config.xml file.
Unable to establish the connection (Error code = 10060)
Code Block | ||||
---|---|---|---|---|
| ||||
<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) |
...
- Check what application uses the port. Make sure that another copy of the application is not running.
- Modify the Listening ports in the engine.properties: ListenPort
DEBUG
...
Incorrect path to the properties file
Code Block | ||
---|---|---|
| ||
<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
Code Block | ||
---|---|---|
| ||
<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
...
Solution 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
Code Block | ||
---|---|---|
| ||
<Timestamp> WARNDEBUG [Engine] "StorageCreationTime" Session <Session_Name> : the telecommunication link error was detected (Connection::receive(), EOF)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
Code Block | ||
---|---|---|
| ||
<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
...
language | bash |
---|
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 | ||
---|---|---|
| ||
<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 | ||
---|---|---|
| ||
<Timestamp> WARN [Engine] Session <Session_Name> : session was created in danger mode - it does not use persistent message storage |
...
In FIXEdge.properties file you can turn on logging for a session by setting 'FixLayer.FixEngine.Session.<SessionName>.StorageType = persistentMM' (or persistent). For Admin Session (a session between FIXEdge and FIXICC Agent) you need to change the property Monitoring.AdminSession.AdminClient.StorageType (which is in engine.properties file) accordingly, but we don’t recommend doing this for Admin Session - there will be quite a lot of messages.
Garbled message
Code Block | ||
---|---|---|
| ||
<Timestamp> WARN [Engine] Garbled message: <FIX_Message> |
Description or root cause
The FIX Protocol takes the optimistic view; it presumes that a garbled message is received due to a transmission error rather than a FIX system problem. Therefore, if a Resend Request is sent the garbled message will be retransmitted correctly. If a message is not considered garbled then it is recommended that a session-level Reject message be sent.
What constitutes a garbled message:
• BeginString (tag #8) is not the first tag in a message or is not of the format 8=FIX.n.m.
• BodyLength (tag #9) is not the second tag in a message or does not contain the correct byte count.
Solution or troubleshooting steps
Make sure that the FIX message was re-transmitted correctly. If not, contact your counterparty regarding malformed messages from their side.
Parse Error: Incorrect size of a repeating group
Code Block |
---|
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 |
Description or root cause
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.
Before FIX Engine version 2.28.1 (and FIXEdge version 6.11.0), this parameter was always enabled.
Solution or troubleshooting steps
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.
...
Code Block | ||
---|---|---|
| ||
<Timestamp> WARN [Engine] Garbled message: <FIX_Message> |
Description or root cause
The FIX Protocol takes the optimistic view; it presumes that a garbled message is received due to a transmission error rather than a FIX system problem. Therefore, if a Resend Request is sent the garbled message will be retransmitted correctly. If a message is not considered garbled then it is recommended that a session-level Reject message be sent.
What constitutes a garbled message:
• BeginString (tag #8) is not the first tag in a message or is not of the format 8=FIX.n.m.
• BodyLength (tag #9) is not the second tag in a message or does not contain the correct byte count.
Solution or troubleshooting steps
Make sure that the FIX message was re-transmitted correctly. If not, contact your counterparty regarding malformed messages from their side.
Parse Error: Incorrect size of a repeating group
Code Block |
---|
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 |
Description or root cause
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.
Before FIX Engine version 2.28.1 (and FIXEdge version 6.11.0), this parameter was always enabled.
Solution or troubleshooting steps
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
Code Block | ||
---|---|---|
| ||
<timestamp> WARN [LogonHandler] <thread> Session <SenderCompId, TargetCompId> : process logon failed - request is timed out |
Description or root cause
This WARN record occurs in the FixEdge.log file if FIXEdge doesn't receive a response in time.
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.
FIXEdge can't create a log directory in the specified path
Code Block | ||
---|---|---|
| ||
<timestamp> WARN [LogonHandlerEngine] <thread> Session <SenderCompId, TargetCompId> : process logon failed - request is timed out: There was an error while creating path <path>. Using default log directory <logDir>. The error reason: <err.message>. |
Description or root cause
This WARN record occurs in the FixEdge.log file if FIXEdge doesn't receive a response in timeif FIXEdge C++ can't create a log directory for the FIX session in the specified path.
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.
...
value of the LogDirectory property specified for this session.
The property was overridden
Code Block | ||
---|---|---|
| ||
<timestamp> WARN [Engine] Session <SenderCompId, TargetCompId>: There was an error while creating path <path>. Using default log directory <logDir>. The error reason: <err.message>The "<property_name>"property was overridden by the file <filename>. |
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 message appears when the value of some property was overridden by another properties file.
Solution or troubleshooting steps
Check the value of the LogDirectory property specified for this sessionThis message can be ignored.
INFO
The active session was closed non-gracefully
...
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
...
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.
...