well, you call it tweaking, I call it ensuring your test environment is
set up properly ;)
e.g. jackrabbit unit tests run with a max heap of 128m
if you want to dive into all the dirty details there are several java
profiler tools that allow you to see the live objects in a jvm...
regards
marcel
Alexandru Popescu wrote:
#: Marcel Reutegger changed the world a bit at a time by saying (astral
date: 2/6/2006 12:13 PM) :#
according to your logs shutdown seems to work fine.
did you try to simply increase the heap space for the jvm? maybe your
settings are just to low for the test cases you are running...
regards
marcel
Instead of tweaking the JVM (I would like to consider this the last
solution), I would like to find out if I can organize somehow else the
tests so that the problem doesn't show.
./alex
--
.w( the_mindstorm )p.
