Matthew Toseland wrote: > I run my nodes in -Xmx100M. Well recently it's been 256 thanks to the > wrapper. Were you downloading many huge files? The JVM will not use a > gigabyte of RAM unless you actually tell it that it can. If it's using > (much) more than your -Xmx setting, then there is a bug _in the JVM_. It > should OOM and fail. So what was your -Xmx setting (if you are using the > wrapper, wrapper.java.maxmemory in wrapper.conf) ?
wrapper.conf: wrapper.java.maxmemory=256 ps axwwwopid,user,state,command : 31110 freenet S java -Xms128m -Xmx256m -Djava.library.path=lib -classpath lib/wrapper.jar:freenet-cvs-snapshot.jar:freenet-ext.jar -Dwrapper.key=PII4PXFbPlyaUE0E -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.pid=31108 -Dwrapper.version=3.2.0 -Dwrapper.native_library=wrapper -Dwrapper.ignore_signals=TRUE -Dwrapper.service=TRUE -Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp freenet.node.Node I'm assuming the 'Resident' size is the one controlled by -Xmx, as that number had never been above 256mb in the past, but now is definitely rising beyond that limit. I will upgrade to Sun Java 1.5.0_07 and see if this takes care of the issue. Thanks! -- Fuzzy love, -CyberLeo Furry Peace! - http://www.fur.com/peace/
