Is it unusual that Derby (used in-memory only) seems to throw an out of memory
exception when executing 180,000 batched insert statements?
(The JVM was started with -Xms1024m -Xmx2048m):
Caused by: java.sql.SQLException: Java exception: 'GC overhead limit exceeded:
java.lang.OutOfMemoryError'.
at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown
Source)
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.javaException(Unknown Source)
at
org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedResultSet.noStateChangeException(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement.setDate(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement.setDate(Unknown Source)
at org.apache.derby.iapi.types.SQLDate.setInto(Unknown Source)
at
org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeBatchElement(Unknown
Source)
Are there memory limitations for Derby running in the in-memory only mode?
Is there anything that can be done to avoid getting such errors?
Thanks,
Pavel.
Jefferies archives and monitors outgoing and incoming e-mail. The contents of
this email, including any attachments, are confidential to the ordinary user of
the email address to which it was addressed. If you are not the addressee of
this email you may not copy, forward, disclose or otherwise use it or any part
of it in any form whatsoever. This email may be produced at the request of
regulators or in connection with civil litigation. Jefferies accepts no
liability for any errors or omissions arising as a result of transmission. Use
by other than intended recipients is prohibited. In the United Kingdom,
Jefferies operates as Jefferies International Limited; registered in England:
no. 1978621; registered office: Vintners Place, 68 Upper Thames Street, London
EC4V 3BJ. Jefferies International Limited is authorised and regulated by the
Financial Services Authority.
