How to tune the amount of SPS Tomcat threads that are unresponsive.

Products

• CA Single Sign On Secure Proxy Server (SiteMinder)
• SITEMINDER

Issue/Introduction

CA Access Gateway (SPS) 12.8 SP1 is newly installed and configured.

The CA Access Gateway (SPS) Tomcat thread count increase is observed. Eventually, it results in a situation where the CA Access Gateway (SPS) became unavailable and unresponsive.

Observation of Tomcat threads counts:

• 6/17: 57 (after SPS startup)
• 6/24: 76
• 9/1: SPS was restarted
• 10/16: 255

How can the embedded CA Access Gateway (SPS) Tomcat can be tuned?

Environment

 

CA Access Gateway (SPS) 12.8SP1

 

Resolution

As for the tuning parameters in the server.conf, below settings, was found (1).

  worker.ajp13.connection_pool_timeout=0

This sets the Maximum time (seconds) that the idle connections will remain in the connection pool before timing out, the default value is 0 which means never time out.

By setting worker.ajp13.connection_pool_timeout to some value such as 600 (10 minutes), the thread count could stabilize.

Additional Information

 

1. Configure the Tomcat Settings Manually
   https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/siteminder/12-8/configuring/access-gateway-configuration/configure-the-tomcat-settings-manually.html