...
| Code Block | ||
|---|---|---|
| ||
<Timestamp> ERROR [CC_Layer] LayerImpl::sendMessage2ClientId() has failed: Message cannot be sent: client TestSMTPClient is not logged in. |
Description or root cause
...
Solution or troubleshooting recommendationssteps
1. First of all, review BL_Config.xml file for the Rule, that routes messages to mentioned Client, and check if it is correct and does what is required by your system. Remove the Rule if there is no need for it.
For instance, the ERROR in this specific example was caused by the default BL Rule which was left unintentionally in place:
...
Solution or troubleshooting recommendations
reconnect Reconnect the session.
New incoming connection was rejected
...
Solution or troubleshooting recommendationssteps
Contact your counter-party for an explanation from their side and related events that make bring more light on the root cause.
Error during processing Logon message
...
Solution or troubleshooting recommendationssteps
- 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.
...
| Code Block | ||
|---|---|---|
| ||
<Timestamp> DEBUG [BL_RoutingTable] No OnActionFail is specified for rule for 'Rule_Name'. |
Description or root cause
...
Solution or troubleshooting recommendationssteps
These are not errors, just indications that the <OnActionFail> condition might be also set up.
WARN
The telecommunication link error
...
| Code Block | ||
|---|---|---|
| ||
<Timestamp> WARN [Engine] Session <Session_Name> : the telecommunication link error was detected (Connection::receive(), EOF). |
Description or root cause
...
Solution or troubleshooting recommendationssteps
Contact counter-party and query them for the sanity of their FIX adaptor/engine.
...
| Code Block | ||
|---|---|---|
| ||
<Timestamp> WARN [Engine] Session <Session_Name> : FixEngine::CreateSession(...) "MessageStorageType storageType" parameter is deprecated. Please use SessionExtraParameters::storageType instead. |
Description or root cause
...
Solution or troubleshooting recommendationssteps
This message can be ignored. To remove this record from the log FIX Antenna user should use the non-deprecated FixEngine::CreateSession method.
...
| Code Block | ||
|---|---|---|
| ||
<Timestamp> WARN [Engine] Session <Session_Name> : session was created in danger mode - it does not use persistent message storage. |
Description or root cause
...
Solution or troubleshooting recommendationssteps
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.
...
Solution or troubleshooting recommendationssteps
Make sure that the FIX message was re-transmitted correctly. If not, contact your counter-party regarding malformed messages from their side.
Parse Error: Incorrect size of a repeating group
...
| Code Block |
|---|
Parse Error : Incorrect size of 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
...
Solution or troubleshooting recommendationssteps
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.
...
Solution or troubleshooting recommendationssteps
Check the incoming FIX session logs and if there are no messages User Response (BF) then the issue is on the Authentification Service side.
...
Solution or troubleshooting recommendationssteps
Ignore, if starting a session without any previous state (For example on the clean log)
...
| Code Block | ||
|---|---|---|
| ||
<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
...
Solution or troubleshooting recommendationssteps
This doesn't indicate an issue, just informs that session was disconnected correctly and sequence numbers were preserved.
...
| Code Block | ||
|---|---|---|
| ||
<Timestamp> INFO [Engine] Session <Session_Name> : Reject task finished. |
Description or root cause
...
Solution or troubleshooting recommendationssteps
This doesn't indicate an issue, just informs that the task was finished.
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
<Timestamp> INFO [Engine] Session <Session_Name> : The backup session has the same parameters as the primary session. |
Description or root cause
...
Solution or troubleshooting recommendationssteps
This message doesn't indicate an issue, just informs that the backup session's parameters are the same as for the primary session.
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
<Timestamp> INFO [Engine] <thread> Session property 'Session.TESTSESSION.StorageType' is not found. PersistentMM storage type is used. |
Description or root cause
...
Solution or troubleshooting recommendationssteps
Make sure that the storage type is specified correctly. Check if there are spaces between the property and its value.