db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Matrigali <mikem_...@sbcglobal.net>
Date Tue, 14 Feb 2012 16:31:20 GMT
Adriano Oliveira wrote:
> Hi,
> Could you please help me with compress?
> Why i aways got an StackOverflowError exception when i try to run CALL 
> I have about 8 tables (consuming 3Gb of disk space) and compress never 
> got success to compress all of then, I'm using the java application 
> CompressAll listed in this 
> wiki http://wiki.apache.org/db-derby/DatabaseConsistencyCheck
> Thans,
> --Adriano
> Java exception: ': java.lang.StackOverflowError'.
>    Causado por: StackOverflowError
> ------------------------------------------------------------------------------------------------
> java.lang.RuntimeException: Java exception: ': 
> java.lang.StackOverflowError'.
> at 
> ... removed stack
Could you post a full copy of the derby.log containing the error. 
Sometimes that log has more information, or previous info in it is 
useful.  Best case would be to log a JIRA as Bryan suggests and put
all info into it.

as a workaround you might try doing one table at a time and committing, 
then going on to the next table.  It should be easy to alter the example
java code, let us know if you need help with that.

This may also reduce the total amount of disk space needed for the
operation.  This operation basically creates a new table and indexes and 
it can not remove the files associated with the old tables and indexes 
until a commit happens.

Also is it at all possible that you
are doing other work in the same transaction?

The DropOnCommit calls are going to
come 1 for each associated object that has a file in derby.  This will
include 1 for each table, index, constraint, and foreign key.  You say
you have about 8 tables, do you have an unusual number of objects
associated with these tables?

Without a repro it is hard to say what is going on.  If I had the db
first thing I would try to see if the problem still exists if there
is not data in the tables, to see if the problem is related to size
of tables, or to ddl of the the tables.

My first question would be if the drop on commit
calls are just too many, or if there is a buggy loop somewhere.

View raw message