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). -- View this message in context: http://old.nabble.com/CALL-SYSCS_UTIL.SYSCS_COMPRESS_TABLE-tp33322411p33357142.html Sent from the Apache Derby Users mailing list archive at Nabble.com.
