Limitation in capacity of XMLNode?

Is there any limitation to the amount of data that can be parsed by the XMLNode module?

We have a workflow that reads a record set from a database then based on a predefined XML template the XMLNode component builds an output file which is then attached to the workflow and eventually published to the production web site.

For most of our sites this is working well - the number of records involved is about 150-200. On one of our sites the recordset is currently 750+ (and growing daily). When the workflow starts it processes about 500 of these records before dying.

I have checked the source data and there is nothing out of the ordinary the would throw an error.

Has anyone else observed anything like this? Its really frustrating the **** out of me..

Cheers

Nathan Wall
Department of Transport and Regional Services (Australia)

Find more posts tagged with

Comments

Johnny

Hi Nathan,

I dont know too much myself, as I havent seen something like this.

I have seen iterative perl code that creates memory leaks though, which eventually hang the app.

So I guess you could check off the code for typical memory leak type stuff.
Eg, ensure references are handled correctly, and are properly scoped/descoped.

The other obvious thing is to check to see how much memory is available before the app runs in its environment (TS workflow environment).
If you are iterating over many dcr's and keeping them in memory, you could be running out of heap space.

They're just a few things i guess.... i dont know of anything myself regarding TeamSite: Smiley Very Happy

CRnode

Let us know how you go!

John Cuiuli
Consultant
Sydney, Australia

Adam Stoller

Can you post, as an attachment, the script that loads/parses all the records - perhaps we might be able to spot a flaw in the logic that would cause the problem being displayed?

--fish
(Interwoven Senior Technical Consultant)