Often just the stack trace for this kind of exception can help a lot,
likely to be in derby.log if you still have it.
Kristian Waagan wrote:
> I have also seen an issue with multi-threaded inserts (25 threads
> against the same table) and a subsequent table compress, but I have to
> investigate further (I was unable to recover the stack trace, I just got
> the error message).
> The table grew to around 20 GB, but the amount of data in it should be
> far less (maybe around 2 GB, ten times less). When compressing, Derby
> threw an IllegalArgumentException, saying "Illegal Capacity: XXX". This
> can look as an overflow or a calculation error when sizing one of
> Vector, ArrayList, or Hashtable.
> I'll try to reproduce and get more information.
>
>
|