How to Adjust Connection Timeout Settings Across All Supported Environments

Introduction

Connection timeout settings play a crucial role in ensuring smooth and uninterrupted user experiences across support environments. Adjusting these settings can help prevent disruptions caused by prolonged inactivity or slow server responses. This guide provides a step-by-step approach to modify connection timeout settings in various support environments.

Steps to Adjust Connection Timeout Settings:

Linux Deployment:

Nginx:

Navigate to the following location: /etc/nginx/sites-available and edit the boldbi-nginx-config or boldreports-nginx-config file to increase the connection timeout.
After updating the configuration, restart NGINX using the following command:
```
 nginx -s reload 
```

Apache:

Navigate to the following location: /etc/apache2/sites-available/ and edit the boldbi-apache-config.conf or boldreports-apache-config.conf file to increase the connection timeout.
After updating the connection timeout, restart Apache using the following command:
```
systemctl restart apache2
```

Docker:

Single container deployment:

Mount the nginx by adding the below line in docker-compose yaml.
```
- nginx_data:/etc/nginx/sites-available  
```
Add the following volume block for NGINX and allocate a directory on your host machine to store the shared folders used by the application. Replace the directory path with <host_path_nginx_data> in the docker-compose.yml file, then bring up the container.
```
  nginx_data:
      driver: local
      driver_opts:
  type: 'none'
  o: 'bind'
  device: '<host_path_nginx_data>' 
```
Navigate to the mounted location and edit the boldbi-nginx-config or boldreports-nginx-config file to increase the connection timeout duration.
After updating the connection timeout, restart the Docker container using the following command:
```
docker restart <container name or container ID>
```

Multi container deployment:

Edit the default.conf file that was used for the multi-container deployment:
Increase the connection timeout value as required:
After updating the connection timeout values, restart the NGINX container using the following command:
```
docker restart <container-name or container ID>
```

Kubernetes Deployment:

Ingress Nginx and NLB Ingress:

Edit the ingress configuration using the following command:

kubectl edit ingress -n <namespace of bold application>

Update the connection timeout-related annotations with the required timeout values, then save the ingress configuration file.

Kong ingress:

Edit the Kong ingress configuration by using the below command:
```
kubectl get ingress -n <namespace of bold application>
```
Update the connection timeout-related annotations with increased time and save the Kong ingress file.

ALB Ingress:

Edit the ingress configuration by using the below command:

kubectl edit ingress -n <namespace of bold application>

Update the connection timeout-related annotations with increased time and save the ALB ingress file.

Traefik:

Edit the traefik configuration by using the below command:

kubectl edit serverstransport long-timeouts-transport -n <namespace of bold application>

Update the connection timeout-related annotations with increased time and save the Traefik ingress file.

Additional Reference:

Was this article useful?

Dislike

Written by Ranjithkumar Chinnadurai

Updated:

Comments (0)