Please clarify the information listed on running smpolicysrv -stats command.
Here is an example of the 'smpolicysrv -stats' which outputs the smps.log when run:
[3524/4640][Sun Sep 17 2017 23:49:55][CServer.cpp:4747][INFO][sm-Serveor-01990] ===================================================================================
[3524/4640][Sun Sep 17 2017 23:49:55][CServer.cpp:4748][INFO][sm-Server-02000] System Statistics
[3524/4640][Sun Sep 17 2017 23:49:55][CServer.cpp:4765][INFO][sm-Server-02020] Thread pool limit: 70
[3524/4640][Sun Sep 17 2017 23:49:55][CServer.cpp:4787][INFO][sm-Server-02030] Thread pool: Msgs=36630 Throughput=0.033/sec Response Time=209.441ms Wait Time In Queue=0.077ms Max HP Msg=2 Max NP Msg=1 Current Depth=0 Max Depth=2 Current High Depth=0 Current Norm Depth=0 Current Threads=8 Max Threads=8 Busy Threads=0
[3524/4640][Sun Sep 17 2017 23:49:55][CServer.cpp:4795][INFO][sm-Server-02040] Connections: Current=0 Max=23 Limit=256 Exceeded limit=0
[3524/4640][Sun Sep 17 2017 23:49:55][CServer.cpp:4798][INFO][sm-Server-01990] ===================================================================================
Deprecated stats information (available in older releases) :
Exceeded limit notes if the maximum agent connection limit has been reached. If further agent connections are attempted (the connections attempted past the limit will be rejected.
Some relevant registry:
Some of this parameter can be configured by modifying the registry (windows registry or sm.registry file on unix)
32 bit : HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Netegrity\SiteMinder\CurrentVersion\PolicyServer\
64 bit : HKEY_LOCAL_MACHINE\SOFTWARE\Netegrity\SiteMinder\CurrentVersion\PolicyServer\
Thread Pool Initial Size
Specifies the minimum number of worker threads that Policy Server opens on startup.
Thread Pool Size
Specifies the maximum number of worker threads that can be opened.
Tcp Max Server Connections
Specifies the maximum number of allowable agent connections.
Default : 256
Number of High Priority Threads. (threads allocated to process high priority handshake messages)
Default : 5
Max : 20
A value less than five or greater than 20 disables the registry key.
Throughput is calculated using Msgs/<second>, where <second> is the number of seconds elapsed since the last Policy Server restart (or when the stats were last cleared, whichever is lower).
Having a "Waits" value that is very close to the "Msgs" value coupled with a low "Misses" value implies that there are enough threads to handle the incoming load, but there are not too many threads configured. A high "Misses" value would indicate that you may have too many threads configured.
A large "Msgs" value coupled with a low "Waits" value and a low "Misses" value would imply that you may need to increase the number of Worker Threads.