On 06/12/2007, at 10:34 PM, Sean Carnes wrote:
The highest that we could set the heap was to 1200. I tried higher and it would not start. It also seemed somewhat unstable above 1024 which was theprevious setting, slowness updating the client and other things. Thecompany that develops the enterprise s/w that uses tomcat said that settings over 1024 were unstable so my feeling was confirmed by them. We use an snmp agent to our nms to get system statistics. There was nothing out of the ordinary, other than tomcat using about 1298M which is the most that we haveseen it use. We have everything up and running now and we are loadbalancing which is how it should have been set up in the first place. The memory usage of tomcat has dropped ~40% since we made that change. It was normally using between 600M & 800M now its down to about 4-500M give ortake.
Hi Sean It seems as if it sort of works at the moment by the sounds of this... Things you can try when you are board and have time: - Does Windows JVM 1.42 have jstat ? - Try upgrading to JVM 1.5 - (linux if not available on windows)- run jstat every minute and you should be able to get a good look at
users vs. memory to see if this is really the problem.
And definitely - upgrade to the 64 bit JVM as soon as possible - RAM
is cheap
Andrew
smime.p7s
Description: S/MIME cryptographic signature
