![]() | ![]() | ![]() | ![]() | ![]() |
If you submit a stored process from a Web browser and close the Web browser before the request has completed execution, in some cases, the SAS Stored Process Server cost might not be reclaimed. Refreshing your Web browser before the original request has completed execution can also prevent the cost from being reclaimed.
When you submit a request, you will see a message, such as the following, written in your SAS Stored Process Server SAS log file:
When the request completes execution, normally the cost is reset to a lower value (such as, cost = cost - 101). For example, the following message should appear in your SAS Stored Process Server log file:
However, in this scenario the cost is not reset to 0; it remains at 101.
If this occurs multiple times while your SAS Stored Process Server is running, the cost might continue to increase until the SAS Stored Process Server cannot accept any more requests.
For example:
When the cost increases multiple times, the following error message might appear in your Web server log:
To avoid or delay this problem (which can disable the server), 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. It is also helpful to specify a Load Balancing Inactivity Timeout for your SAS Stored Process Server; this will enable your SAS Stored Process Server processes to be refreshed when they start again.
These options are accessible from the Server Manager in the SAS® Management Console. Select the Options tab on the property sheet for the stored process logical server.
To change the Maximum Cost Load Balancing value and specify a Load Balancing Inactivity Timeout:
For example, if you specify a value of 60, the SAS Stored Process Server will shutdown after 60 minutes of inactivity.
To change the Cost Per Client value:
NOTE: See SAS Note 17390 "SAS® Stored Process Server problems occur when processing user-written Java or .NET requests that do not close the connection" for a similar problem.
Select the Hot Fix tab in this note for information on how to obtain the hot fix for this issue.
Product Family | Product | System | SAS Release | |
Reported | Fixed* | |||
SAS System | SAS Integration Technologies | Microsoft Windows XP Professional | 9.1 TS1M3 SP1 | |
Microsoft Windows XP 64-bit Edition | 9.1 TS1M3 SP1 | |||
Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M3 SP1 | |||
Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.1 TS1M3 SP1 | |||
Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M3 SP1 | |||
Microsoft Windows 2000 Datacenter Server | 9.1 TS1M3 SP1 | |||
Microsoft Windows 2000 Professional | 9.1 TS1M3 SP1 | |||
Microsoft Windows 2000 Advanced Server | 9.1 TS1M3 SP1 | |||
Microsoft Windows 2000 Server | 9.1 TS1M3 SP1 | |||
64-bit Enabled HP-UX | 9.1 TS1M3 SP1 | |||
64-bit Enabled Solaris | 9.1 TS1M3 SP1 | |||
HP-UX IPF | 9.1 TS1M3 SP1 | |||
Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M3 SP1 | |||
64-bit Enabled AIX | 9.1 TS1M3 SP1 | |||
Tru64 UNIX | 9.1 TS1M3 SP1 |