[FAST-32] The presence map BitVector [byte sequence] has too many bits for the group MDEntries Created: 21/Dec/10 Updated: 07/Oct/11 |
|
Status: | Open |
Project: | OpenFAST |
Component/s: | None |
Affects Version/s: | 0.9.8 |
Fix Version/s: | None |
Type: | Bug | Priority: | Default |
Reporter: | Eduardo Kilhian Armelin | Assignee: | Jacob Northey |
Resolution: | Unresolved | Votes: | 0 |
Labels: | None |
Attachments: | FULL_MESSAGE_20_1292884971843.bin templates-UMDF.xml |
Description |
All, This is my first message and I'm using your solution OpenFAST 0.9.8. In my tests I receive the message below (In more than one UDP package): My question is: This is normal, becouse that is really BIG? Sometimes I can read many MDEntryTipes (73 is my record). Find attached the file with this message: FULL_MESSAGE_20_1292884971843.bin If you need more information, be a pleasure send to you. Thanks in advance, Best Regards, org.openfast.error.FastException: An error occurred while decoding MarketDataSnapshotFullRefresh_20 |
Comments |
Comment by Eduardo Kilhian Armelin [ 21/Dec/10 ] |
This file are related to FAST-32. Thx. |
Comment by Alexandre de Souza Vasconcelos [ 12/Jul/11 ] |
hi Eduardo, I have the same problem. Thx. |
Comment by Glyn Walters [ 06/Oct/11 ] |
I also have this issue. With MarketDataFullRefresh messages from EBSLive (working in other FAST implementation) org.openfast.error.FastException: The presence map BitVector [01110101 11110100] has too many bits for the group MDEntries |
Comment by Glyn Walters [ 07/Oct/11 ] |
After investigation it seems that decodeFieldValues in Group is working correctly when it detects the pmap reader has more bit sets. However it seems in some ECN implementations this may be a valid scenario. We will probably consume this error by creating a new ErrorHandler that ignores it. But it may be worth adding a mode to the decoding that allows more promiscuity if there are extraneous bits in the Group presence map. |
Comment by Jacob Northey [ 07/Oct/11 ] |
There are a couple of different reasons this could be happening.
As a workaround, you can set the global OpenFAST ErrorHandler by using Global.setErrorHandler(ErrorHandler handler). You can then ignore specific FAST error codes. The list of all error codes can be found in org.openfast.error.FastConstants. |