I used a mix of TxXMLFileDescriptorsStore for metadata and JDBCStore for content. The OutOfMemoryError also occured when I built up a repository. Unfortunately I cannot catch a stack trace. There is just none. The only thing I've got is the message "java.lang.OutOfMemoryError".
Regards Stefan
Am Tue, 03 Aug 2004 13:04:23 +0200 schrieb Oliver Zeigermann <[EMAIL PROTECTED]>:
Using the file store? Could you send in the full stack trace that spit out the error?
Oliver
Stefan Fromm wrote:
Hi,
via Slide-API I built up a repository with ca. 6GB (ca. 240,000 resources in ca. 20,000 collections) for performance tests of Slide 2.0. To start the next test the repository is cleaned by deleting the top node containing the whole 6GB. The transaction couldn't be finished because of OutOfMemoryError.
The heap size for the performance tests based on Slide-API was 700MB.
Is this a bug? I would expect Slide to be able to delete a subnamespace regardless of how much to delete. As a workaround I only see to traverse a subnamespace and delete resources one by one. Has this behaviour already changed on the way to Slide 2.1?
Best regards Stefan
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
