Question on Policy Server message queue

Products

• SITEMINDER

Issue/Introduction

Policy Server documentation explains smpolicysrv -stats command output as following (partially excerpted) .

-stats

- Current Depth – Current Depth of the message queue
- Max Depth – Max Depth of the message queue
- Current High Depth – Current depth of the high priority message queue
- Current Norm Depth – Current depth of the normal priority message queue

Here are questions on the message queue.

Q1. What is the max size of the message queue?
Q2. If the number of messages reaches the maximum, what error is logged? And, where?
Q3. Also, even if the number of messages reaches the maximum, and when a new Agent request arrives, how does the Policy Server behave?

Environment

Policy Server

Release : 12.8.05

Resolution

Q1. What is the max size of the message queue?

Message queue size is not fixed in this context. It will vary based on the input message. Messages to policy server is handled in multiple connections, so message queue size will not cause any issues. 

Q2. If the number of messages reaches the maximum, what error is logged? And, where?

No error logged in Policy Server, but it can observed in the -stats.  Policy Server will read only up to max connections. New arriving connections will not logged any error at Policy Server.

Q3. Also, even if the number of messages reaches the maximum, and when a new Agent request arrives, how does the Policy Server behave?

If the Policy Server is busy up to max connections, then Policy Server will not take a new connection until any old connection will finish. If any new connection arrives even after the Policy Server is busy with Max connections, then arrived connection will become closed after initial bind timeout.

Additional Information

Document: Command Line Troubleshooting Options

Related KB: Policy server stats information