Atifah,While it is certainly possible to raise the MaxRequestWorkers value, the error message in the Apache HTTPD error_log is normally only a symptom of a deeper problem. Increasing the MaxRequestWorkers value may not truly contribute to actually solving the root cause.
It is more likely that the problem is high latency happening on other systems. These other systems are usually external LDAP directories like Active Directory or external databases that the SiteMinder Policy Server relies on. When SiteMinder components like the Access Gateway, Web Agents, and the Policy Servers experience high latencies, these are often due to other backend systems and not due to the SiteMinder components themselves.
It is best to follow a "facts and evidence" approach to the problem and follow the observed latencies across the systems by analyzing the trace logs.
For example, if using the SiteMinder Access Gateway to forward/proxy requests after protecting them with SiteMinder, then analyze the Access Gateway agent trace log (configure one in the Agent Configuration Object (ACO)). Check the transactions to see where most of the time is spent - communicating between the Access Gateway and the SiteMinder Policy Server (normally ~1-10ms) or between the Access Gateway and the proxy/forward endpoint.
If it seems that the communications between the Access Gateway/Web Agent and the Policy Server are taking a long time, then compare and correlate the transaction with the Policy Server trace log. Identify the portions of the Policy Server trace log for the transaction where a long time is spent waiting for responses from external resources like databases and/or LDAP directories. Then focus on those end systems to understand why they are performing poorly.
Based on the analysis, following the evidence leads to other systems to understand the root cause.
For the errors observed in the agent log, correlate the timestamps to the SiteMinder Policy Server trace log to try and understand the root cause in more detail.
In my experience, the problems are usually on some external backend system that performs poorly and the SiteMinder components are victims too, experiencing the same high-latency symptoms as the users and their browsers.
Some specific suggestions:
Hope this helps.
Brian DysonIAM Solution Engineering