Execution time exceeded threshold seen in Policy Server logs

Products

• SITEMINDER

Issue/Introduction

When running Policy Server, the smps.log might show more or less often the following INFO message:

Execution time exceeded threshold

This means that the Policy Server takes a longer time than expected to process the Agent request. This can be caused by several disfunction from the environment.

This message has been introduce to help troubleshooting performances issues (1).

 

Resolution

This message can be caused by:

1. Disk space problem on the LDAP Stores:
   
   Performance test environment not working due to slowness in Policy Server
      
2. Lack of file descriptors in Linux Policy Server:
   
   Heavily degraded performance on Policy Servers
      
3. ODBC database problem:
   
   Error: Execution time exceeded threshold with ODBC User Store in PS
      
4. Slow CRL verification:
   
   SiteMinder : Policy server report with "Execution time exceeded threshold user="
      
5. Slow LDAP response:
   
   SiteMinder : Authentication delays for some agent connections
   
   Execution time exceeded threshold errors in Policy Server
   
   Error: Policy Server Execution time exceeded threshold AD
      
6. Execution time exceeded threshold seen in the CA Access Gateway (SPS) Agent logs:
   
   SiteMinder AG : Disabling "Execution time exceeded threshold" messages in WA & AG
      
7. Problems in the LDAP User Store indexes 
   
   Password Change - Status: Error 85 - Time out
      
8. Radius server having issues
   
   Problems with XAuth and execution time
      
9. ODBC Audit Store misconfiguration
      
   Failed preparing audit log insert: Unexpected error in database interface. Error code -1063. Code: -1063. DB Code: 0
      

 

Additional Information

 

1. Siteminder Policy Server what is ExecutionTimeThreshold and why it was Introduced