[This message was posted by Zoltan Vekony of <[email protected]> to the "FAST Protocol" discussion forum at http://fixprotocol.org/discuss/46. You can reply to it on-line at http://fixprotocol.org/discuss/read/413c14b9 - PLEASE DO NOT REPLY BY MAIL.]
The message you have posted in hex seems to be OK: c0 -> PMAP => 1000000 for the TID 81 -> Template Id = 1 => Version Message 23 38 16 80 -> Version Number 81 -> Source Id 02 31 7a c5 -> Sequence Num c0 -> PMAP => 10000000 for the TID f8 -> Template Id = 120 => FAST Reset Message 7f fc -> PMAP => 11111111.11110000 only 12 Bits set (excl. Stop bits) 84 -> Template Id = 4 => Single Leg Reference 80 c0 04 5d d4 b1 01 6c 1d ca 4e 4f 56 ce 4f d0 Maybe you should reset the dictionary manually after decoding the FAST Reset message. Bye Zoltan > Thanks to all. I couldn't solve this issue yet. The exception message > that OpenFast is throwing is: > > org.openfast.error.FastException: The presence map BitVector [00000110 > 00001101 10100000] has too many bits for the group > SingleLegReferenceInformation. > > So I'm assuming that the api is detecting a SingleLegReferenceInfo > message ( TID 4) but suddenly something wrong happens with the pmap. > > > These are the first 32bytes of the message in hex: > > c0 81 23 38 16 80 81 02 31 7a c5 c0 f8 7f fc 84 80 c0 04 5d d4 b1 01 6c > 1d ca 4e 4f 56 ce 4f d0 > > > Can anybody guess what's wrong ? > > > Assuming that OpenFAST is a reasonable application that allows a > > receiver application to decode data stream against a set of templates > > in my opinion the problem is most likely with incorrect templates. > > > > For your information EnBS utilizes maximum 12 PMAP bits in its current > > version. > > > > Regards, Darshan > > > There are a number of ways in which the pmap can have an excess > > > number of bits. That is, more bits than are utilized by the field > > > operators of the template. In an otherwise functional environment a > > > possible reason can be that the template used for decoding is > > > different from the one used for encoding. Other possibilities > > > include a broken encoder or decoder. > > > > > > /David > > > > > > > Hi. I don't know if this forum is the appropriate place to post > > > > this. I'm kinda lost with some openfast issues. I inserted into > > > > the template the FASTRESET message. That allowed me to decode > > > > messages other than the first VERSION msg. EBS is sending a > > > > FASTRESET in between messages. Whenever I get a freset I'm > > > > reseting the openfast context object. My main problem now is with > > > > an openfast exception. I'm receiving a Single Leg Reference > > > > message, some of them are ok and others throw: > > > > > > > > org.openfast.error.FastException: An error occurred while decoding > > > > SingleLegReferenceInformation Caused by: > > > > org.openfast.error.FastException: The presence map BitVector > > > > [00111110 00001000 11110101] has too many bits for the group > > > > SingleLegReferenceInformation > > > > > > > > How is possible for the Pmap to contain more bits that the decoder > > > > is expecting? Can you help me? Openfast people doesn't seem to > > > > read the mailing list that much. > > > > > > > > > > > > Thank you. Augusto. [You can unsubscribe from this discussion group by sending a message to mailto:[email protected]] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/FIX-Protocol?hl=en -~----------~----~----~----~------~----~------~--~---
