The SAS Stored Process Server might not respond when numerous clients 
execute requests that create a large number of sessions.  If you 
experience this problem, the SAS Stored Process Server generally 
recovers within ten to fifteen minutes. 
 
To address this problem, change the "Maximum Cost" Load Balancing value 
for your SAS Stored Process Server from its default value of 1000 to 
500 and change the "Cost Per Client" value from its default of 100 to 1. 
These options are accessible from the Server Manager in your SAS 
Management Console. Select the Options tab on the property sheet 
for the stored process logical server.  For example, in your 
SAS Management Console, do the following: 
 
1. Select: 
 
   Server Manager -> SASMain -> "SASMain - Logical Stored Proess Server" 
 
     -> "SASMain - Stored Process Server" -> Properties 
 
     -> Options -> Advanced Options -> Load Balancing Properties 
 
     Change the "Maximum Cost" value from 1000 to 500. 
 
2. Select: 
 
   Server Manager -> SASMain -> "SASMain - Logical Stored Proess Server" 
 
     -> Properties -> Load Balancing 
 
     Change the "Cost Per Client" from 100 to 1. 
 
If the server still hangs after these changes, you may need to 
increase the number of MultiBridge connections for your SAS Stored 
Process Server. If your SAS Stored Process Server stops and never 
recovers, then the problem is related to a different issue. 
 
The following scenario illustrates the problem. 
 
1.  Your SAS Stored Process Server is running fine. 
 
2.  Numerous client users are running stored processes. Many of the 
    stored processes create sessions. 
 
3.  Suddenly, your SAS Stored Process Server stops executing requests. 
 
4.  After ten to fifteen minutes, the server resumes executing requests. 
 
5.  The SAS Stored Process Server log file contains: 
 
    A.  A "Context close" message for the last user request 
           that occurred before the delay. 
 
    B.  Then, there is a long delay (usually between ten and fifteen 
        minutes), which is followed by the messages: 
 
           STP: Purging Expired Session xxxxxx 
 
           Client connection (xx) closed. 
 
        These messages generally appear multiple times, for multiple 
        sessions and multiple connections. 
 
NOTES 
 
1.  Sessions can be created explicitly or they can be created 
    implicitly. For example, the following statement explicitly 
    creates a session. 
 
       %let rc=%sysfunc(appsrv_session(create)); 
 
    However, as an example, if you create graphics output, a session 
    is generally created implicitly. 
 
    For more information about sessions, see: 
 
http://support.sas.com/rnd/itech/doc9/dev_guide/stprocess/sessions.html 
 
2.  To see the "Context close" and "STP: Purging Expired Session" 
    messages in your SAS Stored Process Server log file, specify 
    applevel=3 for your SAS Stored Process Server. Follow these steps. 
 
    A. In your SAS® Management Console, select Server Manager. 
 
    B. Select your SAS Stored Process Server and "drill down" to the 
       lowest level (for example, SASMain - Stored Process Server). 
       Then, right-click and select Properties -> Options. 
 
    C. On the Object Server Parameters line, specify: 
 
          applevel=3 
 
    D. Save the changes. 
 
    E. Restart your SAS object spawner to activate the changes for your 
         SAS Stored Process Server. 

Operating System and Release Information