search cancel

SPS Tomcat threads amount increase lead to be unresponsive


Article ID: 144625


Updated On:


CA Single Sign On Secure Proxy Server (SiteMinder) SITEMINDER



CA Access Gateway (SPS) 12.8 SP1 is newly installed and configured. The SPS Tomcat thread count increase is observed. Eventually, it results in a situation where SSO became unavailable and unresponsive.
Observation of Tomcat threads count:

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



CA Access Gateway (SPS) 12.8SP1




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


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 an 600 ( 10 min ), thread count could stabilize.


Additional Information



    Configure the Tomcat Settings Manually