Runbook

High % of Busy Threads on Tomcat Host (TEST)

Back to Runbooks

Overview

This incident type is triggered when the percentage of busy threads on a Tomcat host exceeds a certain threshold. This can indicate that the host is experiencing high traffic or that there is a problem with the configuration of the Tomcat server. The incident is resolved when the issue is addressed and the percentage of busy threads returns to a normal level.

Parameters

Debug

List all pods in the namespace

Check the logs of a specific pod

Check the CPU and memory usage of a specific pod

Check the status of the Tomcat service

Check the status of the Tomcat deployment

Check the configuration of the Tomcat server

Improper configuration of the Tomcat server leading to inefficient use of threads and high utilization of the available threads.

Bugs or defects in the application running on the Tomcat server leading to high thread usage.

Diagnostics

  • Increased traffic to the Tomcat server leading to increased thread usage and high utilization of the available threads.
  • Improper configuration of the Tomcat server leading to inefficient use of threads and high utilization of the available threads.
  • Inadequate hardware resources allocated to the Tomcat server leading to high utilization of available threads.
  • Bugs or defects in the application running on the Tomcat server leading to high thread usage.
  • Configuration changes or updates to the Tomcat server leading to unintended consequences that result in high thread utilization.

Repair

Identify and resolve any bottlenecks in the application code that may be causing excessive thread usage.

Check the configuration of the Tomcat server to ensure that it is optimized for the expected traffic volume.

Remediations

  • Check the configuration of the Tomcat server to ensure that it is optimized for the expected traffic volume.
  • Increase the number of threads in the thread pool to handle the increased traffic.
  • Identify and resolve any bottlenecks in the application code that may be causing excessive thread usage.
  • Monitor the thread usage of the Tomcat server regularly to detect any potential issues before they become critical.
  • Implement load balancing to distribute traffic across multiple Tomcat instances to reduce the risk of overloading a single instance.
  • Consider upgrading the hardware or infrastructure supporting the Tomcat server if it is consistently experiencing high traffic levels.
  • Analyze the logs and metrics of the Tomcat server to identify any patterns or anomalies that may be contributing to the high percentage of busy threads.
  • Consult with other team members or subject matter experts to determine if there are any best practices or optimizations that can be implemented to improve the performance of the Tomcat server.

Learn more

Related Runbooks

Check out these related runbooks to help you debug and resolve similar issues.