An extended or high–load use of the SAS^® Stored Process Server can result in an "out of memory" or "insufficient memory" condition that causes the SAS Stored Process Server to fail. The exact threshhold of encountering the problem varies across systems, but available memory can be exhausted over time if the SAS Stored Process Server has been running long enough and it has executed enough SAS^® Stored Processes that contribute to the memory leak.

Errors similar to the following are usually found in the middle-tier web server or the SAS Stored Process Server log files when this problem occurs:

2011-11-09T13:54:29,372 ERROR [00262674] 9939:webanon@saspw - STP_ERR: Failed to
create stpmv environment, Context ID: 1111.

2011-11-09T13:54:30,739 ERROR [00262760] 9928:webanon@saspw - STP_ERR: Server
CreateContext Failed to Create Session Scope, Context ID: 2222.

STP: The STP MVA scope for context cannot be accessed.

STP: The MVA Workspace cannot be accessed.

The SAS^® Metadata Server log file can contain errors similar to the following when the SAS Stored Process Server memory is exhausted and SAS Stored Processes fail to execute:

2011-11-09T13:54:22,688 ERROR [00000010] :SYSTEM@MYSERVER - The Bridge Protocol Engine Socket Access 
Method listen thread failed to schedule the activity for connection xxxx.

2011-11-09T13:54:22,688 ERROR [00000010] :SYSTEM@MYSERVER - Failed to process peer request.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Applying this hot fix is REQUIRED for all 9.3TS1M0 and 9.3TS1M1 BI installations that use a SAS Stored Process Server.

Operating System and Release Information

A fix for this issue for SAS Integration Technologies 9.3 is available at:

A fix for this issue for SAS Integration Technologies 9.3_M1 is available at: