Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Overview

This article provides information about log messages related to validation and parsing errors.

Validation

Validation collects the errors until the end of the message, groups them per type, and then reports each group in one row of the log file.

  • Unrecognized tags are found in the message

    The following tag(s) is not defined for this message type: <tag number1>, ..., <tag numberN>; <tag_numberNN> in Group<lead_tagNN>, Entry #=<entry_numberNN>[Nested group <lead_tagM>, Nested entry #=<entry_numberM>],[...]. Error(s) in message <message_type> with sequence number <seq_number>.

    Description: All found unrecognized tags in the message are reported in one row of the log file. 


  • Empty tags are found in the message

    The following tag(s) is specified with no value: <tag number1>, ..., <tag numberN>; <tag_numberNN> in Group <lead_tagNN>, Entry #=<entry_numberNN>[Nested group <lead_tagM>, Nested entry #=<entry_numberM>],[...]. Error(s) in message <message_type> with sequence number <seq_number>.

    Description: All found empty tags in the message are reported in one row of the log file.


  • Tags with the incorrect data format are found in the message

    The following tag(s) is specified with no value: <tag number1>, ..., <tag numberN>; <tag_numberNN> in Group <lead_tagNN>, Entry #=<entry_numberNN>[Nested group <lead_tagM>, Nested entry #=<entry_numberM>],[...]. Error(s) in message <message_type> with sequence number <seq_number>.

    Description: All found tags with the incorrect data format in the message are reported in one row of the log file.

  • Required tags are missed in the message

    The following required tag(s) is missing: <tag number1>, ..., <tag numberN>; <tag_numberNN> in Group <lead_tagNN>, Entry #=<entry_numberNN>[Nested group <lead_tagM>, Nested entry #=<entry_numberM>],[...]. Error(s) in message <message_type> with sequence number <seq_number>.

    Description: All missing required tags in the message are reported in one row of the log file.


  • Component blocks are empty in the message

    The following required tag(s) is missing: <tag number1>, ..., <tag numberN>; block <block_name1> (<req_tag number1>, ..., <req_tag numberN>),... ,block <block_nameN> (<req_tag number1>, ..., <req_tag numberN>); <tag_numberNN> in Group <lead_tagNN>, Entry #=<entry_numberNN>[Nested group<lead_tagM>, Nested entry #=<entry_numberM>],[...]. Error(s) in message <message_type> with sequence number <seq_number>.

    Description: All empty component blocks in the message are reported in one row of the log file and displayed as part of the Required tags are missed error message.

WARN

  • Myricom DBL is not supported

    <Timestamp>    WARN    [Engine]  Myricom DBL is not supported. Cannot load dynamic library: 'dbltcp.dll'. The specified module could not be found. (Error code = 126)

    Description: These records in log file are about compiler options which were used to build FixAntenna library. FixAntenna checks if Myricom card is installed and available.

    Troubleshooting steps: This doesn't indicate an issue. Please, ignore them.

  • Message queue was overflown

    <Timestamp>    WARN    [b2bits_mfix_instrument]  orders CURR CETS|USD000UTSTOM: Message queue was overflown.

    Description: This record appears when number of messages stored in recovery mode for the particular instrument becomes more than maximum.

    Troubleshooting steps: You should increase MDApplicationParams::incrementQueueSize_ parameter or handle messages quicker.


  • No labels