The Remote Services application defaults to a 64M heap. If you run 200 users through the Information Delivery Portal and those users run Stored Processes, Web reports, etc., the Remote Services application will get an OutOfMemoryException. This occurs because each remote session context consumes ~350K of memory.

Starting with SAS 9.1.3 SP3, install.properties variables and additional JVM parameters have been added to control the Remote Services heap size.

The SAS Services application is used by the SAS Information Delivery Portal to pass session and user context to content viewers, remote portlets, and Web applications launched from the portal (for example, SAS Web Report Viewer). This Java application allows the user to seamlessly pass through to the target without the requirement for a separate logon. By default, its JVM options are set to handle a moderate number of concurrent users, in the neighborhood of 750 - 1000. To support a larger number of concurrent users, the minimum and maximum heap size of the SAS Services application, -Xms and -Xmx respectively, will need to be increased. The application will need approximately 128 MB of additional memory for every additional 750 - 1000 users.

To increase the minimum and maximum heap size of the SAS Services application, add the following properties to the end of the install.properties file located in the PortalConfigure subdirectory of the Portal's installation directory. For example, on a typical Windows installation this directory would be:

The values shown below will increase the minimum and maximum heap size to 256 MB.

After updating the properties file, perform the following steps:

1. Stop the Application server running the Portal Web application and the SAS Services application.
2. Run the configure_wik utility to update the SAS Services application's memory configuration.
3. Restart the SAS Services application.
4. Restart the Application server.

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

Operating System and Release Information

A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

A fix for SAS 9.1.3 (9.1 TS1M3) with Asian Language Support (DBCS) for this issue is available at :