The default timeout for the SAS Stored Process Web Application servlet is 900 seconds, or 15 minutes. To change the timeout for the SAS Stored Process Web Application servlet (that is, when you are using /SASStoredProcess/do? to submit a stored process from a Web client), you must edit the web.xml file found on the middle-tier server in the servlet WEB–INF directory. For example, under Tomcat the path might look like these samples below:

UNIX platforms:

Windows platforms:

Once you have located the SASStoredProcess/WEB-INF/web.xml file, edit the file and add the following block with the desired timeout specified in seconds:

The init param must be included in the <servlet> section of the web.xml file as follows:

Once the edited file is saved, you must stop and restart the servlet container for this change to be picked up. You should also delete the SASStoredProcess temporary cache directory under the servlet container to ensure that the new content is used. For example, under Tomcat the directory by default is:

Note: If the Web Infrastructure Kit (WIK) is redeployed, the changes made to the web.xml file under the servlet container will be lost when the file is deployed again. Additional information is included below.

To include the SessionTimeout modification when the WIK is redeployed, edit the web.xml file found in the following locations:

UNIX platforms:

Windows platforms:

The configure_wik.bat (Windows) or configure_wik.sh script (UNIX) must be resubmitted and the recreated WAR files must be redeployed. Refer to the wik_readme.html file for instructions on deploying the Web applications to the servlet container.

Operating System and Release Information