Access Gateway error : Server ran out of threads to serve requests. Consider raising the ThreadsPerChild setting

Products

• SITEMINDER

Issue/Introduction

 

There is scenario where the Access Gateway goes down very frequently and doesn't allow connections to it and is impacting users accesing the backend application via Access Gateway

In the httpd.log file of Access Gateway we can find as below

[05/16/2023][19:52:23][18464][572][...][getConnection][No connections available for [{s}->https://_host.example.com.:443] Found In-Use = true]
[05/16/2023][19:52:23][18464][13112][...][getConnection][No connections available for [{s}->https://_host.example.com:443] Found In-Use = true]

 

Environment

Product : Access Gateway 

Release : 12.8.x

Cause

 

All the worker threads of the HTTPD component of Access Gateway is getting engaged and no spare worker threads available to accept new incoming client requests to reach backend. Below is the log snippet from the apache logs.

[Fri Jun 02 18:37:17.219183 2023] [mpm_winnt:notice] [pid ####:tid ###] AH00354: Child: Starting 150 worker threads.
[Mon Jun 05 11:17:47.130632 2023] [mpm_winnt:error] [pid ####:tid ##] AH00326: Server ran out of threads to serve requests. Consider raising the ThreadsPerChild setting

 

Resolution

 

-> Stop the Access Gateway services 

-> Navigate to httpd conf directroy and

-> Increased max worker threads set to a desired value or double the existing value of worker threads in the httpd-mpm.conf

This will accommodate the Access Gateway httpd component  to accept the new incoming clients request.

-> Start the Access Gateway services.