PMAP decoding issues

augustoacuna_x · March 20, 2009, 8:10pm

Imported from previous forum

augustoacuna_x · March 20, 2009, 8:10pm

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.

declancaulfield_x · March 20, 2009, 8:38pm

Can you post your packet bytes - that doesn’t look right…

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.

davidrosenborg30_x · March 22, 2009, 6:29pm

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.

fplpo_x · March 23, 2009, 4:17pm

[ original email was from Darshan Khedekar - darshan.khedekar.ext@deutsche-boerse.com ]
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.

augustoacuna_x · April 8, 2009, 9:40pm

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.

jacobnorthey_x · April 8, 2009, 9:48pm

The reason the error is thrown is because the presence map contains more bits than is allowed for the given template. In the error below there are 16 bits in the presence map. The template must contain less than 16 fields that occupy the presence map.

The source of the error is hard to determine without more context. The underlying issue could be:

a frame shift error in OpenFast,
an encoding error
incompatible templates between the sender and receiver

There are potentially more issues. If you are unable to determine the root cause, feel free to contact me offline.

Jake

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.

declancaulfield_x · April 9, 2009, 6:25am

I haven’t used OpenFAST but to me it looks like the PMAP bytes are 0x7CFC => PMAP = 11111001111100.

c0 f8 is the reset and that is followed by pmap and TID 0x84.

Hope this helps.

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.

fplpo_x · April 9, 2009, 6:38am

[ original email was from Zoltan Vekony - zoltan.vekony@web.de ]
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.

Topic		Replies	Views
FAST decoding error can anyone help me.? imported , fast-protocol , xid_169567	6	184	January 9, 2012
Eurex Bit Stream. imported , fast-protocol , xid_169776	2	61	January 15, 2010
swx MDI decoding issue imported , fast-protocol , xid_169753	15	39	May 15, 2009
pmap doubt imported , fast-protocol , xid_169694	6	31	September 11, 2008
Help with pmap imported , fast-protocol , xid_169597	4	66	February 19, 2010

PMAP decoding issues

Related topics