TOMCAT5 appears to be using much more memory than it should need and eventually becomes unresponsive. Our only solution is to restart the service. We've looked around for a KB article, but only found the Java heap error. That fix is for a clustered environment and did not help.
How can we manage the memory usage of TOMCAT service?
Our server manages roughly 8,000 hosts and a decent amount of rollup data. There are several global reviewers at any given time running SQL queries through the web interface.
Joe, we have since upgraded to 4.6.7.
Same thing is happening in 4.6.7. Tomcat periodically grows to above 1,200,000 kb and then becomes unresponsive or slow. Is there any way to manage this?
In that case I'd open a case with support, as troubleshooting this type of issue is complex. If the problem is simply down to load, and you're getting heap memory errors, then one possibility would be to upgrade to ePO 5.x: this uses a 64bit version of Tomcat which can address way more memory than the 32bit version in previous ePO versions.