Re: [Quickfix-users] Duplicate EncryptMethod field in Logon Message

[Oren M. <or...@qu...>]

Are you perhaps accidentally adding n EncryptMethod field to the header?

--oren

On Jan 19, 2007, at 2:56 PM, Robert Parrott wrote:

> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/ 
> html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
> Hi Folks,
>
> I'm finding that the outgoing Logon message from my code, using
> quickfix 1.12.4 (actually later from SVN) is setting the EncryptMethod
> field 98 twice.
>
> This is causing a counterparty to reject to logon attempt.
>
> Has anyone seen this before?
>
> I'm using quickfix with the python bindings, and am finding that in
> the quickfix callback fromApp, the message itself doesn't show this
> duplicate field, but the mesage logged by quickfix, and thae message
> actually sent over the wire, has this extra field.
>
> Looking at the source, I see that in the Logon message class (i.e.
> fix42/Logon.h)  this field is set when the Logon class is
> instantiated. Then in Session.cpp, I see that this field is set again.
> I guess I'd assume that it wouldn't end up with duplicate fields, but
> that's what I'm seeing.
>
> Any thoughts?
>
> rob