> It builds, but dies when I try to run it because of some
> Avalon configuration mistake that I don't understand the
> finer points of.
Check the differences in assembly.xml and config.xml between the 2.2.0 and
current trunk.
> Without going into specific details or requiring a lot of
> hand
Given that the whole crash starts with: java.lang.OutOfMemoryError, then
maybe that caused the problem with derby.
From the derby list, 64MB for it only looks like not enough.
Does anyone know anything about derby's behaviour when it runs out of
memory? I'd imagine that these errors are caught
> I am still concerned about the Derby related crash that I saw earlier.
> Anyone have a clue? And is there anything that we need to do to cleanly
> shut Derby down?
>
> --- Noel
Given that the whole crash starts with: java.lang.OutOfMemoryError, then
maybe that caused the problem with derb
