There's a setting on the appserver you need to change using 'blasadmin':
set asset maxconfigrecords 70000
there's a couple other similar settings in 'AppServer' section in blasadmin
ok, this is old, but:
do you know what exactly IS a "config record" or - more exactly - what is counted as one of these 70.000?
We have a snapshot-job which fails with the same error and in the .../WorkItem-Thread-#######.ini-file there are a bit more than 2000 <record>-entries with one containing a VERY long line of xml-type data. Splitting all these <xml-type-data><xml-type-data><xml-type-data>... in seperate lines leads to a file with about 28.000(!) lines.
Extended Object Output
Config file Output
i should have replied two days ago, at 5:28pm, that would have been sweet.
> i should have replied two days ago, at 5:28pm, that would have been sweet.
> Extended Object Output
> Config file Output
Yes, the actual case is the output of the os_config.nsh-script. For some servers this is beyond the limit. To have an idea to which value we should change the MaxConfigRecords-value, I want to calculate how much we exceeded the 50000-limit. I counted lines - they are over 50000 - but this makes no real sense. I counted "<record>"-entries in the output. That were less than 50000. So there must be something in between. That's why I asked for some exact "definition".
how did you count 'record' - w/ wc -l? or individual occurances of record?
I first splitted all xml-items in separate lines with something like
%s/></>\n</ (in vi, maybe it was not \n but \r - after all "some linebreak")
On that edited file I ran something like
grep '<record>' filename | wc -l
i think there are more than just record lines that make up the input.
bottom line is there is too much input for the appserver to handle. i'm not sure how exactly to calculate the exact number. i'd also look at what's in the data, and why it's so large..