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

Products

• SITEMINDER

Issue/Introduction

Access gateway gets down very frequently and doesn't allow connections to it

There is no traffic from the frontend which is getting logged in the httpd.log file we can find:

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

Environment

Release : 12.8.x

Cause

As per the below Apache logs the Apache is reaching thread limits.

[Fri Jun 02 18:37:17.219183 2023] [mpm_winnt:notice] [pid 12996:tid 464] AH00354: Child: Starting 150 worker threads.
[Mon Jun 05 11:17:47.130632 2023] [mpm_winnt:error] [pid 12996:tid 4344] AH00326: Server ran out of threads to serve requests. Consider raising the ThreadsPerChild setting
[Mon Jun 05 11:18:00.132881 2023] [mpm_winnt:warn] [pid 12996:tid 4344] (OS 64)The specified network name is no longer available.  : AH00341: winnt_accept: Asynchronous AcceptEx failed.

Resolution

Access Gateway's Apache component needs to have more mpm thread count to resolve this issue.

-> Increase the number of mpm threads in the file httpd-mpm.conf  based on the user request load you receive.

-> stop / start the access gateway services.