Slowness and massive loopback hits identified in SPS logs.
search cancel

Slowness and massive loopback hits identified in SPS logs.


Article ID: 367390


Updated On:


CA Single Sign On Secure Proxy Server (SiteMinder) SITEMINDER


When running a CA Access Gateway (SPS), this one stop responding to the requests. A restart is needed to get the service available again.

The access.log from the embedded Apache service, shows a lot of redirect between /index.html and / request from and - - [26/Apr/2024:00:13:10 +0200] "GET /index.html HTTP/1.1" 302 - - - [26/Apr/2024:00:13:10 +0200] "GET / HTTP/1.1" 302 -



The proxyrules.xml show 2 problems.

The default forward and redirect don't specify a destination server:



  [...omitted for brevity...]

As per documentation, a destination server should be specified (1):

Access Gateway forwards a request to a destination, or sends a redirect response to a user that specifies a destination. A set of proxy rules must contain destinations that can be reached according to the conditions and cases defined in the proxy rules.

Define a backend server to make the CA Access Gateway (SPS) handling correctly those default request.



  • For both nodes, determine a destination server in both proxyrules.xml for the default;
  • Restart both the CA Access Gateway (SPS).


Additional Information