db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Matrigali <mikem_...@sbcglobal.net>
Subject Re: CALL SYSCS_UTIL.SYSCS_COMPRESS_TABLE
Date Mon, 20 Feb 2012 17:45:39 GMT
Matthew McCawley wrote:
> 
> Mike Matrigali wrote:
>> You see the same kind of repeated stack in the error?  This loop looks 
>> strange to me, and I don't think should be related to size of the tables:
>>   at 
>> org.apache.derby.iapi.store.raw.xact.RawTransaction.notifyObservers(Unknown 
>> Source)
>> at org.apache.derby.impl.store.raw.data.DropOnCommit.update(Unknown
>> Source)
>> at java.util.Observable.notifyObservers(Observable.java:142)
>>
> 
> I see exactly this loop of repeated errors. 
> http://old.nabble.com/file/p33357142/derby.log derby.log 
> 
> 
> Mike Matrigali wrote:
>> There are some reported problems with the amount of memory in general 
>> that compres table uses, which are likely to be a different issue.  For
>> these memory issues it is helpful to post exactly what jvm you are 
>> using, what OS, and what flags you are giving the jvm.  And how much 
>> memory is on your machine.
>>
> 
> I'm running on Windows 7 64bit with 8 GB of RAM and am not passing any
> arguments to the JVM. It fails unless I pass in -Xss2048k (I think the
> default is 512k).
I have reported DERBY-5624 to track this issue.  I think I understand 
the problem, but would feel much better with a reproducible test case
I could run.  Feel free to add your information to DERBY-5624.

Mime
View raw message