Scott Carey wrote:
Yes, I see the same thing.Adding maxmemory="128m" to the junit ant task fixed it for me.
I wonder if what we're actually seeing is an exhaustion of file descriptors due to some leak. As I recall, this also shows up as an OOM.
Another way to fix this, rather than adding maxmemory, is to remove forkmode="once", so that a new JVM is forked per test. That also fixes it for me.
Doug
