---
id: 8afd516a-8485-43cb-b830-cd929bddc46e
---

# Tomcat Server Crash
---

Tomcat Server Crash incident type refers to a situation where the Tomcat Server, an open-source web server and servlet container, becomes unresponsive and stops functioning. This can result in a complete or partial system outage, leading to a disruption in the delivery of web applications and services. The root cause of the crash can be attributed to a variety of factors such as misconfiguration, network or hardware issues, software bugs, or excessive server load. It is critical to address this incident quickly to minimize the impact on users and restore normal system functionality.

### Parameters
```shell
export SERVER_IP="PLACEHOLDER"

export PID="PLACEHOLDER"

export PATH_TO_TOMCAT_CONFIG_FILE="PLACEHOLDER"

export MINIMUM_MEMORY_ALLOCATION="PLACEHOLDER"

export MAXIMUM_MEMORY_ALLOCATION="PLACEHOLDER"
```

## Debug

### Check if Tomcat is running
```shell
systemctl status tomcat.service
```

### Check the Tomcat logs for errors
```shell
tail -n 100 /var/log/tomcat/catalina.out
```

### Check the system logs for any related errors
```shell
dmesg | grep tomcat
```

### Check if there are any resource limitations that might be causing the crash
```shell
free -m

df -h
```

### Check the Tomcat configuration files for any errors
```shell
cat /etc/tomcat/server.xml
```

### Check the version of Java being used by Tomcat
```shell
java -version
```

### Check the installed packages for any updates that may have caused the crash
```shell
apt list --installed | grep tomcat
```

### Check for any file permission issues
```shell
ls -l /var/log/tomcat/
```

### Check if there are any firewall or networking issues
```shell
netstat -anp | grep 8080

ping ${SERVER_IP}
```

### Check for any memory leaks in the Tomcat server
```shell
jmap -heap ${PID}
```

### Check the CPU usage and load averages
```shell
top
```

## Repair

### Restart the Tomcat server to see if it comes back online.
```shell


#!/bin/bash



# Stop Tomcat server

sudo service tomcat stop



# Start Tomcat server

sudo service tomcat start


```

### Verify that there is enough memory allocated to the Tomcat server and adjust as necessary.
```shell


#!/bin/bash



# Set the path to the Tomcat server configuration file

TOMCAT_CONFIG_FILE=${PATH_TO_TOMCAT_CONFIG_FILE}



# Set the minimum and maximum memory allocation for the Tomcat server

MIN_MEM=${MINIMUM_MEMORY_ALLOCATION}

MAX_MEM=${MAXIMUM_MEMORY_ALLOCATION}



# Check the current memory allocation for the Tomcat server

CURRENT_MEM=$(grep -oP '(?<=Xmx)\d+m' $TOMCAT_CONFIG_FILE)



# If the current memory allocation is less than the minimum, adjust it to the minimum

if [[ $CURRENT_MEM -lt $MIN_MEM ]]; then

  sed -i "s/-Xmx${CURRENT_MEM}m/-Xmx${MIN_MEM}m/" $TOMCAT_CONFIG_FILE

fi



# If the current memory allocation is greater than the maximum, adjust it to the maximum

if [[ $CURRENT_MEM -gt $MAX_MEM ]]; then

  sed -i "s/-Xmx${CURRENT_MEM}m/-Xmx${MAX_MEM}m/" $TOMCAT_CONFIG_FILE

fi



echo "Tomcat server memory allocation has been adjusted."


```

Tomcat Server Crash incident type refers to a situation where the Tomcat Server, an open-source web server and servlet container, becomes unresponsive and stops functioning. This can result in a complete or partial system outage, leading to a disruption in the delivery of web applications and services. The root cause of the crash can be attributed to a variety of factors such as misconfiguration, network or hardware issues, software bugs, or excessive server load. It is critical to address this incident quickly to minimize the impact on users and restore normal system functionality.


When too many requests are sent to a Tomcat server, the thread pools that handle these requests can run out of available threads. This means that incoming requests will not be processed, leading to service degradation or even a complete outage. This incident type is critical for web applications that rely on Tomcat as their application server.


Tomcat thread pool exhaustion.

This incident type usually occurs when there is a failure in the SSL Handshake process between a client and server running on a Tomcat web server. This can happen for various reasons such as incorrect SSL certificate configuration, cipher suite mismatches, or network connectivity issues. When this type of incident is not resolved quickly, it can lead to downtime or service disruptions for users trying to access the affected service.


Tomcat SSL Handshake Failure Incident

This incident type occurs when the PermGen or Metaspace usage of the Tomcat server exceeds 90%. PermGen and Metaspace are memory pools used for storing class definitions and metadata of the Java virtual machine (JVM). When these memory pools reach their maximum capacity, the server may experience performance issues or even crash. This incident requires immediate attention from the software engineer to investigate the root cause and take appropriate actions to resolve the issue.


Tomcat PermGen or Metaspace Usage exceeds 90%

This incident type is related to the Tomcat server, which is a popular open-source Java application server. It occurs when the available threads in the connection pool are running low, which means that there are not enough resources to serve incoming requests. This can cause delays or even failures in the application's performance, impacting the end-user experience. It is important to monitor and address this issue promptly to ensure that the application runs smoothly and efficiently.


Tomcat Low Available Threads in Connection Pool

In software engineering, a large number of suspended threads in Tomcat is an incident type that occurs when a high number of threads are created but are blocked from executing. This can happen due to a variety of reasons, such as slow database queries, network latency, or resource contention. When this occurs, the system may become unresponsive or slow, causing a degradation in performance or even a complete system failure. It is important to investigate and resolve this issue as quickly as possible to ensure the system can continue to function properly.


Tomcat Large Number of Suspended Threads Incident.

```shell
export SERVER_IP="PLACEHOLDER"

export PID="PLACEHOLDER"

export PATH_TO_TOMCAT_CONFIG_FILE="PLACEHOLDER"

export MINIMUM_MEMORY_ALLOCATION="PLACEHOLDER"

export MAXIMUM_MEMORY_ALLOCATION="PLACEHOLDER"
```


### Check if Tomcat is running

```shell
systemctl status tomcat.service
```

### Check the Tomcat logs for errors

```shell
tail -n 100 /var/log/tomcat/catalina.out
```

### Check the system logs for any related errors

```shell
dmesg | grep tomcat
```

### Check if there are any resource limitations that might be causing the crash

```shell
free -m

df -h
```

### Check the Tomcat configuration files for any errors

```shell
cat /etc/tomcat/server.xml
```

### Check the version of Java being used by Tomcat

```shell
java -version
```

### Check the installed packages for any updates that may have caused the crash

```shell
apt list --installed | grep tomcat
```

### Check for any file permission issues

```shell
ls -l /var/log/tomcat/
```

### Check if there are any firewall or networking issues

```shell
netstat -anp | grep 8080

ping ${SERVER_IP}
```

### Check for any memory leaks in the Tomcat server

```shell
jmap -heap ${PID}
```

### Check the CPU usage and load averages

```shell
top
```


### Restart the Tomcat server to see if it comes back online.

```shell


#!/bin/bash



# Stop Tomcat server

sudo service tomcat stop



# Start Tomcat server

sudo service tomcat start


```

### Verify that there is enough memory allocated to the Tomcat server and adjust as necessary.

```shell


#!/bin/bash



# Set the path to the Tomcat server configuration file

TOMCAT_CONFIG_FILE=${PATH_TO_TOMCAT_CONFIG_FILE}



# Set the minimum and maximum memory allocation for the Tomcat server

MIN_MEM=${MINIMUM_MEMORY_ALLOCATION}

MAX_MEM=${MAXIMUM_MEMORY_ALLOCATION}



# Check the current memory allocation for the Tomcat server

CURRENT_MEM=$(grep -oP '(?<=Xmx)\d+m' $TOMCAT_CONFIG_FILE)



# If the current memory allocation is less than the minimum, adjust it to the minimum

if [[ $CURRENT_MEM -lt $MIN_MEM ]]; then

  sed -i "s/-Xmx${CURRENT_MEM}m/-Xmx${MIN_MEM}m/" $TOMCAT_CONFIG_FILE

fi



# If the current memory allocation is greater than the maximum, adjust it to the maximum

if [[ $CURRENT_MEM -gt $MAX_MEM ]]; then

  sed -i "s/-Xmx${CURRENT_MEM}m/-Xmx${MAX_MEM}m/" $TOMCAT_CONFIG_FILE

fi



echo "Tomcat server memory allocation has been adjusted."


```


Tomcat Server Crash

Overview

Parameters

Debug

Check if Tomcat is running

Check the Tomcat logs for errors

Check if there are any resource limitations that might be causing the crash

Check the Tomcat configuration files for any errors

Check the version of Java being used by Tomcat

Check the installed packages for any updates that may have caused the crash

Check for any file permission issues

Check if there are any firewall or networking issues

Check for any memory leaks in the Tomcat server

Check the CPU usage and load averages

Repair

Restart the Tomcat server to see if it comes back online.

Verify that there is enough memory allocated to the Tomcat server and adjust as necessary.

Learn more

Related Runbooks

Tomcat thread pool exhaustion.

Tomcat SSL Handshake Failure Incident

Tomcat PermGen or Metaspace Usage exceeds 90%

Tomcat Low Available Threads in Connection Pool

Support