Garbage Collector Problem

Hi Etienne
 
 
I found the reason and also the solution for my garbage collector
problem:
When I use --verbose-gc I see that a initial heap of 16MB is allocated
when the vm is started but the system where sablevm is running on
doesn't have so much free memory. So I guess that the VM runs out of
memory before it launches the garbage collector.
Now I use --property="sablevm.heap.size.min=500000" and
--property="sablevm.heap.size.max=800000" and with the --verbose-gc
option. Now there are gc traces "[verbose gc: ...]" every time the heap
is full and the system's free memory moves between two nearly constant
values. That's exactly what I need!
 
But I have a new problem, which is trivial I guess but I can't find the
solution: My app needs a native library that is located at
/usr/java/lib. In the first version I used java-sablevm to launch my
app. Please see the shell-script "do_java" how I set classpath and
library path. To use the extended options like above I use now sablevm
to launch. But it can't find the native library anymore saying
"java.lang.UnsatisfiedLinkError: Native library .... not found in
gnu.classpath.boot.library.path and java.library.path". Please see
"do_sable" how I set up. I also tried out the
"sablevm.boot.class.path.append" property with no effect.
So the question is, how do I correctly translate the java-sablevm call
into the sablevm call so that the native library is found?


Regards
Marco

_______________________________________________
SableVM-user mailing list
[email protected]
http://sablevm.org/lists/control/listinfo/sablevm-user