Posted: Mon Apr 07, 2008 7:23 am Post subject: TDS parsing problem in MBv6.0
Novice
Joined: 12 Apr 2007 Posts: 10
Hi,
I have a a message which occurs as an unorderedSet in the following manner :
field1;4;ABCD;field2;2;DF;
and I have defined a TDS parser to parse the same. I have noticed that whenever I pass the message in this format ->
field1;4;ABCDEF;field2;2;DF;
the parser throws an exception saying that message bit stream is larger than expected.
while the following message ->
field1;4;ABCD;field2;2;DFGHJIKL;
is processed safely and sent to the output, with field2 being assigned as 'DF' while the broker ignores the extra bytes.
I am using v6 version of the broker and wanted to know the reason for this odd behavior. The expected result was an error in both the situations. Is there any workaround for the last situation, so that I get an error thrown by the parser for the same?
How are we supposed to know that they are 'extra'. You haven't told us how many there ought to be!
Please
- describe your message format, including length and number of occurrences for each field.
- post an example message and the message tree that you want to end up with.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum