Agent Trace shows Policy Server with negative capacity

Agent Trace shows Policy Server with negative capacity

book

calendar_today

Products

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

Issue/Introduction

[07/21/2023][15:35:48][15:35:48.780][3100][8544][][Server 192.168.0.1: Current total capacity: -485, current throughput: 4951
[07/21/2023][15:35:48][15:35:48.780][3100][8544][][Server 192.168.0.2: Current total capacity: 38.5, current throughput: 3.61
[07/21/2023][15:35:48][15:35:48.780][3100][8544][][Server 192.168.0.3: Current total capacity: 41.9, current throughput: 1.38
[07/21/2023][15:35:48][15:35:48.780][3100][8544][][Selected server 192.168.0.3: Current total capacity: 40.5, current throughput: 1.38][SmClient.cpp:3054][GetServer][][][][][][][][][][][][][][][][][][][][][][3][][][ACTIVE][3]

Why is the Policy Server capacity becoming negative?

Release : 12.8.x

Cause

This is when "EnableFailover=NO" in HCO or Clustering is used.

A rough formula is

Capacity = {Previous Capacity} - ( {Throughput} + {NewRequest} )
Throuput = {Previous Throuput} + {New Request}

To simplify things, this is based on a configuration where Policy Server has only 1 worker thread.

The Capacity can be negative when the Throughput value becomes greater than the Capacity.

Example:
Current stat: Capacity is 50, Throughput is 50

Then:
Capacity = {Previous Capacity} - ( {Throughput} + {NewRequest} )
= 50 - (50 + 1)
= -1

Resolution

This is by design.

Note: