Re: [basex-talk] RESTXQ - java.lang.OutOfMemoryError: Java heap space

2020-06-02 Thread Christian Grün
Hm… Yes, maybe the number of inserts is simply too large for single insert operations. Did you count how many new cases will be created? > into doc("US") Are you inserting into a document or a database? In the latter case, you could replace the function call with db:open. The db:copynode option

Re: [basex-talk] RESTXQ - java.lang.OutOfMemoryError: Java heap space

2020-05-29 Thread Sebastian Guerrero
Hi Christian, Thank you for your reply, you always help me. *- Can you share the query with us?*. Yes, of course. The query is pretty much the same that I've sent to Fabrice: *(# db:copynode false #) {* * for $case in

Re: [basex-talk] RESTXQ - java.lang.OutOfMemoryError: Java heap space

2020-05-29 Thread Christian Grün
Hi Sebastian, In general, artifacts of updating queries should be cleaned up after the execution. The stack trace indicates that a very large main-memory database instance was created by one of your queries that exceeded the memory limits. Can you share the query with us? As XQuery is more

Re: [basex-talk] RESTXQ - java.lang.OutOfMemoryError: Java heap space

2020-05-29 Thread ETANCHAUD Fabrice
Hi Sebastian, There is a prof:gc() function, but that should only be used for debugging purposes. Is your Pending Update List applied to the collections after each call (do you see your changes in the db inbetween calls) ? I had memory overflow issues during xquery update functions calls, but