[Quickfix-developers] QuickFIX bug.

[Nicholas P. <nic...@sl...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have discovered a bug in QuickFIX when dealing with the 355 tag in the 
Email message. I am working with a vendor who has chosen to embed Custom 
FIX tags within the 355 block of an email message. QuickFIX does not 
parse this message correctly at all.

Instead of looking at the 354 tag and determining the length of the 355 
tag from that, it instead assumes that the next <eos> after the start of 
the 355 tag indicates it's end. While the embedding of FIX within a tag 
like the 355 tag is a dubious choice, I have to receive these message. I 
will endeavor to make a patch for this bug.

The other bug I have found has to do with the way the BodyLength is 
calculated. The message I receive from this vendor has a tag that is 
repeated, once outside of a repeating group, and once within. QuickFIX 
incorrectly calculates the body length by only counting this repeated 
tag once, and thus rejects the message outright.

Finally, a question on QuickFIX internals. I have noticed that there is 
a distinct lack of logging within the various components that make up 
QuickFIX. For example, when a message is rejected due to a bad 
BodyLength or Checksum QuickFIX prints no error messages at all? Another 
example would be in parsing the XML file for validation, if there is an 
error in the XML it prints an error, but not the tag that caused it, 
making diagnosis of the problem much more difficult. Is there any reason 
for this? Is there a canonical way to log from within other QuickFIX 
modules that I could use to log these errors?

Thanks,
- -Nick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE+kbgDR42/Somtp0QRAsCPAJ90HWqJmF5TcJ38tCkNUT+bHlNpOgCeJroN
U2qGT1VcZIE/+nKuNvwKQJQ=
=Kcgv
-----END PGP SIGNATURE-----