wsedio wrote:
On 20-05-2004 11:58, wsedio wrote:
On 19-05-2004 23:15, Michiel Toneman wrote:
We were having severe memory problems too with 5.0.19.
Does Tomcat 5.0.24 fix this problem?
I have no idea, haven't tried it out yet. No plans as yet to test/roll-out 5.0.24, so it will be a while before I know.
We added this to the jk2.properties:
request.registerRequests=false
and the memory usage was normal again. Somewhat non-obvious, I agree. It also gets rid of "Error registering request" messages in catalina.out. We are using mod_jk (1.2) with Apache 1.3.x on Sun Solaris and Linux.
Do you have to add the setting even if you are using jk 1.2 (not jk 2)?
Apparently so. Somewhat weird that it is in jk2.properties. Any Guru care to explain?
Below is the memory profile of one of our servers before and after the change ("old generation memory" refers to the memory buckets in the garbage collector. For more information, see jvmstat. At 100% you will start getting OutOfMemory errors):
How do you get the memory profile? Is it a Tomcat command?
No, it is just a bit of messing around with jvmstat in a script.
First we get the Tomcat PID with jvmps. Then we use jvmsnap $TOMCAT_PID to get (grep)
hotspot.gc.generation.1.space.0.capacity
and
hotspot.gc.generation.1.space.0.used
The script then calculates the percentage in use and total amount in Mb.
The old generation space usage is (as far as I know) a good place to look if you are experiencing memory problems (assuming you set -Xmx and -Xms memory the same, otherwise it isn't all that meaningful!!!). In my experience, if it fills up above 70% the garbage collector (+ you) is in trouble.
Cheers,
Michiel
--
Michiel Toneman Software Engineer Bibit Global Payment Services Regulierenring 10 3981 LB Bunnik [EMAIL PROTECTED] Tel. +31-30-6595168 Fax +31-30-6564464 http://www.bibit.com/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
