Hi Ciaran, 

thank you for your hints.
I tried with "ulimit -a" and got

time(seconds)        unlimited
file(blocks)         unlimited
data(kbytes)         4293918720
stack(kbytes)        392192
memory(kbytes)       unlimited
coredump(blocks)     4194303

I used "top" for checking the RAM usage. The problem seems to be xercesc
depending, 
because there is enough virtual memory and a background process 
using 100MB doesn't change the result, it measn, 
unknow exception when reading xml, when 672-674MB used.
Can it be the stack? I am not sure.

Greetings

Thomas


Ciaran McHale wrote:
> 
> Hi Thomas,
> 
> At 11:39 24/08/2006, thomak wrote:
>>I tried to read large XML files using DOM on HP, using version .27.
>>Until 20 MB it works fine, but there is a limit, that I get,
>>when the structure gets bigger, it means also, the file is mostly bigger
>>too.
>>Problem:
>>During reading, the Reader (see below) quit reading returning exception.
>>It happens, when the process acheived the mark of 674 MB of used RAM.
>>I tried it on different machines and it is allways the same.
>>Is there a memory limit for xerces?
> 
> I don't know whether or not Xerces has any limits in the size of files
> that it can process. However...
> 
> Perhaps the problem is not in Xerces but rather in the amount of virtual
> memory available to your process. Type "man ulimit" to look at the manual
> page for the "ulimit" command. In particular, your system administrator
> might have placed a limit on the amount of virtual memory available to
> applications. You can check for this with "ulimit -v". From memory, I
> think the command to unset this limit is "ulimit -v unlimited". Another
> possibility might be that the entire computer is running out of virtual
> memory. If the "top" command is available on your computer then run it in
> one shell window while running your application in another windows, and
> look at the details in "top" regarding the amount of virtual memory or
> swap space that is available. If this shrinks close to zero then lack of
> virtual memory is your problem.
> 
> 
> Regards,
> Ciaran.
> --
> Ciaran McHale, Ph.D.        Email: [EMAIL PROTECTED]
> Principal Consultant        Tel: +44-(0)7866-416-134 (mobile)
> IONA Technologies, UK       Tel: +44-(0)118-954-6632 (home office)
>                              Fax: +44-(0)118-954-6767
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/xercesc-dom-input-structure-size-limit%2C-RAM-limit--tf2157920.html#a5962003
Sent from the Xerces - C - Users forum at Nabble.com.

Reply via email to