----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
Increasing the memory on java startup doesn't help, I assume?
Have you tried running under a profiler like JProbe or OptimizeIt?
These are very helpful, and we've solve a bunch of memory leaks in our
code with them. Anytime we've suspected some Java or JServ thing
leaking, it's always been our fault.
We're also running Solaris 2.7, 1.2.2_05a on all of our machines (all
E250 or E450). We have a similar startup command:
nohup /usr/java1.2/bin/java -mx128m -classpath $classpath org.apache.jserv.JServ
/v/telebiz.com/ma/billo/conf/jserv.properties >>$outfile 2>&1 &
Good luck...
billo
From: "Ed Crotty" <[EMAIL PROTECTED]>
Date: Wed, 23 Aug 2000 11:21:10 -0400
----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
we are running :
1 e450 2 cpus / 1.2 gig memory
1 e4500 8 cpus / 1 gig memory
java version "1.2.2"
Solaris VM (build Solaris_JDK_1.2.2_05a, native threads, sunwjit)
solaris 7 on both boxes..
each box has a webserver and a jserv instance on it... the web servers
are loadbalanced on the front end and the jservs are load balanced to
one another via jserv.conf settings..
everything ROCKS (thanks jserv team), but during VERY heavy load, we
start to get memory issues...in the logs we will see things like :
Ran out of space for compiled code.
Current size is 16777216 bytes.
Increase code space with -Xmaxjitcodesize
here's the non standard stuff we have in our jserv start script (we are
running in manual)
ulimit -n 1024
java -Xms128m -Xmx256m org.apache.jserv.JServ $properties $1 2>> $log
is there some other flags we should be looking into using? it seems
that whenever we get low (under 100 megs low) on available pshyical
memory, things start to get crazy and we get IO exceptions... is this
simply we need more pshyical memory to play with or could the code be
more optimized to use what we currently have? should we push up our
memory settings passed to java when starting jserv?
or is there some tool we can use to probe into the jserv to see what
objects are taking up so much space and how they are being used... what
would be a reasonable tool for doing this...
my first gut feeling is throw some more memory at it.. but im not sure
its neccessary?
thanks!
-ed
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search Archives:
<http://www.mail-archive.com/java-apache-users%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search Archives:
<http://www.mail-archive.com/java-apache-users%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
