CODEWITHSUNDEEP
quickfixfix-protocol
Jonathan Livni
Jonathan Livni

Reputation: 107062

capturing incoming FIX messages which fail QuickFix validation

A Quickfix client validates incoming messages using XML spec files. If a message fails validation, quickfix automatically sends a rejection response. AFAIK in this case quickfix does not call the standard callback for incoming messages fromApp(), so up till now I was unable to programatically capture these erroneous incoming messages and handle them.

Is there a way to capture incoming FIX messages which fail quickfix validation?

Of course they may appear in the default quickfix log files, but I would rather capture them in my code in realtime.

Upvotes: 9

Views: 3531

Answers (2)

cengizkrbck
cengizkrbck

Reputation: 704

Validation via XML spec file is in session level processing. So, there is not suitable hook for this.

On the other hand, there are some configuration parameters;

  • UseDataDictionary : eliminates validation
  • ValidateUserDefinedFields : eliminates user defined field's validation

look for detailed descriptions

edit: If your real problem is monitoring rejections, capturing Reject(3) and BusinessReject(j) messages at toAdmin() hook is sufficient.

Upvotes: 1

Grant Birchmeier
Grant Birchmeier

Reputation: 18484

There is not.

QuickFIX simply does not consider this a useful feature. If a message is invalid, QF performs the protocol-specified behavior and there is nothing that the application could or should do to recover. Any fix will require developer analysis and xml and/or code fixes, thus log files are sufficient to record the issue.

If you would like an automated alert when such errors occur, I suggest perhaps some kind of external log monitoring app that could watch your logs for occurrences of 35=3 or 35=j. (On the cheap side, a composition of cron/grep actions could do this very easily.)

Upvotes: 5

Related Questions