<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-size:small;color:rgb(0,0,0)">Yeah, SetField is a basic function that's used a million times.</div><div class="gmail_default" style="font-size:small;color:rgb(0,0,0)"><br></div><div class="gmail_default" style="font-size:small;color:rgb(0,0,0)">It would be more informative to trace at SendRaw and/or GenerateLogon. You can look at the generated Logon message to see if it looks funny with regard to 35. (Though I can't imagine why it would.)</div><div class="gmail_default" style="font-size:small;color:rgb(0,0,0)"><br></div><div class="gmail_default" style="font-size:small;color:rgb(0,0,0)">-Grant</div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Nov 8, 2022 at 12:28 PM Francis Gingras <<a href="mailto:francis@collective2.com" target="_blank">francis@collective2.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">A recompile using the latest QF source code (sept 8 2022) did not result in anything different. I used the stock FIX50SP2.xml. The only major change I had to do was to charge OrdType from CharField to StringField to accomodate a broker's misuse of the field (they decided to send more than one character in tag 40).<br><br>I tried to trace QuickFix.FieldMap.SetField but there are 82,000+ references and VS CodeLens died :-))<br><br>Francis<br><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Nov 8, 2022 at 12:35 PM Francis Gingras <<a>francis@collective2.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Yes I agree with your observation.<br><br>I've been using QF for about 15 years and it's a great tool. The last time I recompiled QF 1.10 using the Ruby tool was a year ago to add some custom fields to 4.2.<br><br>The build works well with < FIX 5.0, but this is the first time I tried 5.0 since 2016. I will rebuild it today to see if I get different behavior and report back.<br><br>Francis<br><br>-------------------------<br><br><pre style="white-space:pre-wrap;color:rgb(0,0,0)">(Is QuickFix/n 1.10*.1*.0 a typo? The latest is just 1.10.0)
This is weird. It looks like this is happening when your app tries to
construct and send the logon message to the counterparty. Do you agree
with that observation?
If that is correct, then the MessageCracker is not to blame-- it's not even
used yet when this error occurs. If your app doesn't send a Logon, then
the counterparty won't send a Logon back or any other messages, so there's
nothing to crack.
I'm a little stumped as to why this could happen. This whole process
should be happening internally in the engine. (I'm not even sure how a dev
could doink it up with weird app code.)
Let me ask around. Please reply if you get any other ideas.</pre></div>
</blockquote></div>
_______________________________________________<br>
Quickfixn mailing list<br>
<a>Quickfixn@lists.quickfixn.com</a><br>
<a rel="noreferrer">http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr"><div><font size="2"><span style="background-color:rgb(0,0,0)"><span style="background-color:rgb(255,255,255)">Grant Birchmeier</span></span></font><font size="2"><font color="#3333ff"><br></font></font></div>Connamara Systems, LLC<div><font size="2"><a href="http://connamara.com" target="_blank">http://connamara.com</a><br></font></div></div></div>
<br>
<span style="color:rgb(29,28,29);font-family:Slack-Lato,appleLogo,sans-serif;white-space:pre-wrap;background-color:white"><font size="2">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.</font></span>