Posted: Thu Mar 04, 2004 7:15 am Post subject: Conversion error 'The field length was less than maxLen'
Newbie
Joined: 12 Nov 2002 Posts: 6
A 'The field length was less than maxLen' error was experienced when a 100 length XML field was being converted to a 100 length MRM field. The solution has worked for months and had no problems but has recently failed.
On inspection of the 100 bytes of data it was noticed that the data contained a '£' sign and was thus converted to a 'A£' by default when the XML was created. Consequently the field length was 101.
One would expect the broker to convert (back to '£') and then validate the data length, however, in this case the broker must validate the length before converting and hence produces an error message (slightly misleading though it is).
Has anyone else experienced this sort of error and if so what solutions are available?
I assume you are using validation on a compute/mapping node or input node. Correct ? Which ?
Validation is done on the logical message tree. So the data is always in UTF-8 when it is validated. The actual input or output bitstream is not validated.
Quote:
On inspection of the 100 bytes of data it was noticed that the data contained a '£' sign and was thus converted to a 'A£' by default when the XML was created. Consequently the field length was 101.
What does this mean ? was 'A£' present in the data before it was parsed by the broker ?
I suggest you post some more detailed information, like the input XML message and traces of the message tree either side of the compute/mapping node.
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