FIX message contains bad character, how can we skip it

[DHirani]

We have certain brokers sending us a FIX message where the tag 58 value contains invalid characters that causes the FIX engine to stop with "Invalid message: Expected ..."

Session FIX.4.4:TEST->CLIENT disconnecting: QuickFix.InvalidMessage: Invalid message: Expected BodyLength=797, Received BodyLength=795
at QuickFix.Session.Next(MessageBuilder msgBuilder)
at QuickFix.SocketInitiatorThread.ProcessStream()
at QuickFix.SocketInitiatorThread.Read()

Workaround

1. Stop FIX engine and jump the sequence number by one.

Is it possible to extend QuickFixN so it delivers the payload as bad message then jumps to the next message?

[stbrd]

Running into the same exact issue but with a different tag (65). Would like to reject the invalid message and move on to the next, but QuickFixN stops and cannot move to subsequent messages without manual intervention.

[machonky]

Ouch! I got the same error when an extended character was passed through on Tag 58.

QuickFix.InvalidMessage: Invalid message: Expected BodyLength=392, Received BodyLength=388
at QuickFix.Session.Next(MessageBuilder msgBuilder)
at QuickFix.SocketInitiatorThread.ProcessStream()
at QuickFix.SocketInitiatorThread.Read()

The partial text in question contained a Finish word: "päivä". Something is going wrong in the serialization of extended characters.

Upstream, the text/data is just passed through. I wouldn't deem this text invalid.

Looks like this issue is solved with an update: http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/2021q3/001371.html

[gbirchmeier]

Yes, if you are not using QF/n 1.10, please upgrade and try again.