Christopher Shultz wrote: // Time to upgrade. Tomcat is hideously out of date (probably because you are using RedHat's Tomcat package), at least by version number. I'm not sure what RedHat does (if anything) about security fixes, etc. but a vanilla 6.0.18 is probably vulnerable and has been for a very long time.
Java 1.6 is EOL and Java 1.7 is getting close. I strongly advise you to move up to Tomcat 8.0.20 and Java 1.8 and start developing and testing your application against those versions. // Would if I could. Vendor restriction. I can only run what they will support. Christopher Shultz wrote: // > Typical startup options looks like this... > > JAVA_OPTS="-Xms192M -Xmx384M \ -XX:MaxPermSize=128M \ Those seem reasonable, except maybe not PermGen. Are you increasing it or reducing it from the default on your platform? // Increased from default of 64 MB, which ran fine for years until a recent software upgrade. Christopher Shultz wrote: // > The memory allocation seems low to you because we run many instances > of tomcat on the same server. Although the servers have 32-64GB of > RAM, the individual tomcat/java instances are kept fairly low. We ran for years in a 64MiB heap. Then we got enough traffic that sessions required us to expand our heaps. If you can run in a small heap, great. But keep your eye on what's happening with your users; you may find that you have outgrown your old heap settings. // That's what this question is about. We ran 64 MB heaps for years, but with the latest application software version we find that 192-384 is required per instance. Others throw errors unless they get 768. We cannot set them all the same, so we need to configure them very carefully and closely. Christopher Shultz wrote: // > We are trying to be proactive by watching the memory usage numbers in > the thread dumps. Heap dumps? // What we do is called a thread dump, as far as I know. We use kill -3 on Linux, which dumps the thread activity. The memory data shows up at the bottom of that. See: http://producthelp.sdl.com/WorldServer/10.2/en/GUID-4F09CD10-BC4F-46A8-AE83-599A5C8C7740.html --Eric
