RE: [Exist-open] High memory usage inserting large numbers of documents

[Paul L. <Pau...@ds...>]

The garbage collection calls were still in 1.0b1.=20

Since the JVM should have plenty of memory available at this point, I'm
don't think that it's running out of memory.=20

I've been a little swamped with other things at the moment, however I've
managed to run it through jdb, catching the OutOfMemoryError.=20

Exception occurred: java.lang.OutOfMemoryError=20
(to be caught at: org.exist.xmldb.LocalCollection.storeXMLResource(),
line=3D493 bci=3D191)
       "thread=3Dmain", org.exist.collections.Collection.addDocument(),
line=3D748 bci=3D872

If I'm reading this right, it shows the location of the catch/finally
block rather than the memory allocation line that failed. This isn't
very useful, but it's better than nothing. It doesn't always fail in the
same place.=20

The call stack is:
main[1] where
  [1] org.exist.collections.Collection.addDocument (Collection.java:748)
  [2] org.exist.collections.Collection.addDocument (Collection.java:616)
  [3] org.exist.xmldb.LocalCollection.storeXMLResource
(LocalCollection.java:486)
  [4] org.exist.xmldb.LocalCollection.storeResource
(LocalCollection.java:433)

Locals:
main[1] locals
Method arguments:
broker =3D instance of org.exist.storage.NativeBroker(id=3D906)
name =3D "48405"
data =3D "<DScribeRecord><RecordType>Component</RecordType>
... ----- >8 Lines cut >8 ------
</DScribeRecord>"
privileged =3D false
Local variables:
oldDoc =3D null
lock =3D instance of org.exist.util.ReentrantReadWriteLock(id=3D903)

I'll keep looking at it, adding some additional logging.=20

Regards,


Paul