[FIXED in 2.2.20100930.0] faulty vvOut_toJSON with VVTREEDS

[MasterH]

Good day

When we use the vvout_toJSON function
to output a big JSON tree structure (about 2000 nodes)
the resulting output text appears to be 'chopped' in
some locations (for example, approximately at 64K boundary,
a bunch of characters are trimmed out)

---- OUTPUT SNIPPET -----
misc2:"CONF10£",
misc3:"*MHP",misc90020002800490029",
leaf:true,misc2:"CONF15£"
---- OUTPUT SNIPPET -----

In the example above, the 'misc9' property of a node
get mixed with part of the text description of the next node,
and it happens at the 65396th byte.

The same behaviour occurs multiple times across the
resulting output text.
I suspect there's a bug in the buffer handling of the VVOUT
routines. Can you help me figure it out ?

Thanks in advance.
Stefano Maini
Master House Srl

[richard.milone]

Thanks for posting this. We will take a look at it within the next few days. It's quite possible there might be something going wrong at the 64K point. Valence 2.2 is coming out later this month so if we can find and identify a bug we will fix it for that release.

[sean.lanktree]

What version of Valence are you running? I believe this issue was already fixed with the latest release....

http://cnxforum.com/showthread.php?t=363

[MasterH]

We already installed Version 2.1.20100802.0
on a iSeries 515 V6R1 system.

Apparently, the "Bug with large output streams" issue is still present.
The bug involves the output of a large JSON Tree structure.

[sean.lanktree]

Can you take a look at the source code for VVOUT. Line 193.00 should be constant MAXOUT. What value is this set to?

[MasterH]

the line says:

d MAXOUT c const(65530) 100713

[sean.lanktree]

We were able to replicate your problem and the fix will be included in the next release (due later this week).

[richard.milone]

Fixed in Valence 2.2.20100930.0.