db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Deering (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5981) Derby INSERT Eats Stack Space, Causes java.lang.StackOverflowError
Date Mon, 05 Nov 2012 20:58:12 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490919#comment-13490919

Tom Deering commented on DERBY-5981:

Disregard, I think I have a solution I can live with:

(1) Turn off auto-commit.
(2) Use PreparedStatement for all inserts.
(3) ExecuteUpdate() for each row, then call connection.commit() at the end.

It's still not the fastest thing I've ever seen, but ~7100 rows/second on insert isn't too
> Derby INSERT Eats Stack Space, Causes java.lang.StackOverflowError
> ------------------------------------------------------------------
>                 Key: DERBY-5981
>                 URL: https://issues.apache.org/jira/browse/DERBY-5981
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions:
>         Environment: Ubuntu Linux 12.04.1 64-bit, Sun Java 1.7.0_09, Derby
>            Reporter: Tom Deering
>            Priority: Minor
> Apache Derby causes a java.lang.StackOverflowError with large INSERT statements.
Here, "large" means 5000+ rows. I am using Derby in my Java application with the EmbeddedDriver
in the following way:
> Class.forName("org.apache.derby.jdbc.EmbeddedDriver").newInstance();
> Connection connection = DriverManager.getConnection("jdbc:derby:<db path>;create=true;upgrade=true")
> String insertString = buildSQLInsertString();
> Statement stmt = connection.createStatement();
> stmt.execute(insertString); // StackOverflowError
> I have tried calling this in different ways, including with PreparedStatement. I have
also tried increasing derby.storage.pageSize, to no effect. If I increase the VM argument
-Xss to something insanely big, then after ~30 seconds I get:
> SQL Error: Statement too complex. Try rewriting the query to remove complexity. Eliminating
many duplicate expressions or breaking up the query and storing interim results in a temporary
table can often help resolve this error.
> My code works fine for smallish inserts, but overflows the stack for anything modestly
large. I can't tell if Derby is using an unreasonably large amount of stack space with INSERT,
or if the size of what I am inserting is unreasonable.
> I'm a newcomer to database development and also to Apache Derby, so suggestions for details
to make this bug report more useful would be welcome.
> EDIT: I updated my code to insert in chunks of at most 1000 rows at a time. This seems
to be a viable workaround... but I'm still interested in inserts using a single statement
and wondering if there is a bug with Derby's INSERT.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message