{{Quickfixn}} FIX message contains bad character, how can we skip it

Wed Aug 18 14:04:08 PDT 2021

I apologize for not speaking up earlier.  Yes, there was a known issue with
special characters in older builds.  In 1.9.0, we enhanced QF/n to support
the full iso-8859-1 character set.

The current QF/n release is 1.10.  If you are not using it, I strongly
suggest updating.

(Technically per FIX spec, counterparties should not be sending non-ASCII
characters in non-"EncodedXXX" fields, but too many FIX counterparties just
do whatever they want...)

On Wed, Aug 18, 2021 at 3:56 AM Marc Allaume <mallaume at infin.fr> wrote:

> Hi,
>
>
>
> Same here ! Also very interested if any safer solution is possible…
>
>
>
> Marc
>
>
>
> *De :* Quickfixn <quickfixn-bounces at lists.quickfixn.com> *De la part de*
> Jiho HAN
> *Envoyé :* mardi 17 août 2021 21:53
> *À :* Mailing list for QuickFIX/n <quickfixn at lists.quickfixn.com>
> *Objet :* Re: {{Quickfixn}} FIX message contains bad character, how can
> we skip it
>
>
>
> I ran into the same issue last Monday and we used the same workaround but
> only after some damage was already done.
>
> It looks like 1.9.0 fixes the issue for us, at least for the particular
> issue we ran into (umlaut a in tag 58) but should it happen again in some
> other manner, I don’t have much confidence that we won’t be left with
> another mess to clean up.
>
>
>
> I would also love an option to skip/mark the message and move on since we
> are mostly a drop copy shop, one bad message lost isn’t that big of a deal.
>
> Disconnecting the session as it does now seems like a very drastic move
> for a bad message.
>
>
>
> Thanks
>
> Jiho
>
>
>
> Classification: Confidential
>
>
>
> *From:* Quickfixn <quickfixn-bounces at lists.quickfixn.com> *On Behalf Of *Toomey,
> Sean
> *Sent:* Wednesday, August 11, 2021 7:09 PM
> *To:* quickfixn at lists.quickfixn.com
> *Cc:* Vincent, Brad <Brad.Vincent at broadridge.com>
> *Subject:* [EXTERNAL] {{Quickfixn}} FIX message contains bad character,
> how can we skip it
>
>
>
> Hi All,
>
>
>
> Looking for some advice on how to handle this situation (
> https://github.com/connamara/quickfixn/issues/683), raised by someone
> else earlier this year but I just ran into it earlier today.
>
>
>
> How can malformed messages be rejected and bypassed in code? Right now it
> seems the only solutions are no validation or manual intervention. Thanks.
>
>
>
> Issue defined below:
>
> *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?*
>
>
>
>
>
>
>
> *Sean Toomey* | Development Manager, Securities Finance Collateral
> Management | Broadridge Financial Solutions, Inc.
> p +1 413-395-9511 | m +1 413-281-2180
>
> <https://www.linkedin.com/company/broadridge-financial-solutions>
> <https://twitter.com/broadridge>
> <https://www.youtube.com/user/BroadridgeInsights>
> <https://www.facebook.com/BroadridgeCareers>
>
> *broadridge.com <http://www.broadridge.com/>*
>
>
>
> This message and any attachments are intended only for the use of the
> addressee and may contain information that is privileged and confidential.
> If the reader of the message is not the intended recipient or an authorized
> representative of the intended recipient, you are hereby notified that any
> dissemination of this communication is strictly prohibited. If you have
> received this communication in error, please notify us immediately by
> e-mail and delete the message and any attachments from your system.
>
>
> This message and any attachments (the "message") is intended solely for
> the addressees and is confidential. If you receive this message in error,
> please delete it and immediately notify the sender. Any use not in accord
> with its purpose, any dissemination or disclosure, either whole or partial,
> is prohibited except formal approval. The internet can not guarantee the
> integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will)
> not therefore be liable for the message if modified. Please note that
> certain functions and services for BNP Paribas may be performed by BNP
> Paribas RCC, Inc.
>
>
> Unless otherwise provided above, this message was sent by BNP Paribas, or
> one of its affiliates in Canada, having an office at 1981 McGill College
> Avenue, Montreal, QC, H3A 2W8, Canada. To the extent this message is being
> sent from or to Canada, you may unsubscribe from receiving commercial
> electronic messages by using this link: www.bnpparibas.ca/en/unsubscribe/.
> See www.bnpparibas.ca for more information on BNP Paribas, in Canada.
> _______________________________________________
> Quickfixn mailing list
> Quickfixn at lists.quickfixn.com
> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com
>

-- 
Grant Birchmeier
*Connamara Systems, LLC*
*Made-To-Measure Trading Solutions.*
Exactly what you need. No more. No less.
http://connamara.com

-- 
This email, along with any attachments, is confidential. If you believe you 
received this message in error, please contact the sender immediately and 
delete all copies of the message. Thank you from Connamara Systems, LLC.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20210818/fef31dee/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 728 bytes
Desc: not available
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20210818/fef31dee/attachment-0008.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 741 bytes
Desc: not available
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20210818/fef31dee/attachment-0009.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 726 bytes
Desc: not available
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20210818/fef31dee/attachment-0010.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 715 bytes
Desc: not available
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20210818/fef31dee/attachment-0011.jpg>