How to Tune Tomcat
Last updated on JUNE 09, 2017
Applies to:APM - Application Performance Management - Version 6.5.0 to 6.5.5 [Release 6.5]
Information in this document applies to any platform.
This knowledge note is only applicable to BTM release 6.x.
Oracle BTM provides with its products an Apache Tomcat servlet container. Release 6.0 and higher comes with Tomcat 5.5.
Depending on your use of BTM products, you might need to tune the Tomcat container in which they run. For example, the performance of an agent that handles a very high rate of client traffic usually benefits greatly from increased container resources.
Signs that an agent or other component requires more container resources include but are not limited to:
- "out of memory" errors
- increased response time as client traffic increases
- “timeout" errors in response to client requests
- occasional pauses in Tomcat processing
- rejected requests, resulting in this processor error in your Tomcat logs:
To address these issues, the two resources that require tuning are the number of threads that process requests and the amount of available memory, i.e., Java heap size. The former is controlled by Tomcat itself, whereas the latter is controlled by the underlying Java Virtual Machine (JVM).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms