Problem Note 64260: SAS® Studio orphaned workspace-server processes are not being cleaned up based on the value of the HTTP session time-out interval
Workspace-server processes that are generated by SAS Studio might be orphaned if a user exits a SAS Studio session in an unsupported manner.
The supported method of exiting SAS Studio is by using the Sign Out button. Methods that can create orphaned processes are closing the browser tab without signing out or closing the browser window directly.
SAS Studio should clean up any orphaned processes based on the value of the HTTP session time-out interval, which is set in the web.xml file for the application server.
For the SAS® Studio Enterprise Edition, the file is in this location:
SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer2_1/conf/
For the SAS® Studio Basic Edition, the file is in this location:
SAS-configuration-directory/studioconfig/appserver/studio/conf/
In the web.xml file, the time-out interval setting is in this section:
<session-config>
<session-timeout>30</session-timeout>
</session-config>
As shown here, the default setting is 30 minutes.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Studio | Windows 7 Ultimate x64 | 3.7 | | 9.4 TS1M5 | |
Windows 7 Ultimate 32 bit | 3.7 | | 9.4 TS1M5 | |
Windows 7 Professional x64 | 3.7 | | 9.4 TS1M5 | |
Windows 7 Professional 32 bit | 3.7 | | 9.4 TS1M5 | |
Windows 7 Home Premium x64 | 3.7 | | 9.4 TS1M5 | |
Windows 7 Home Premium 32 bit | 3.7 | | 9.4 TS1M5 | |
Windows 7 Enterprise x64 | 3.7 | | 9.4 TS1M5 | |
Windows 7 Enterprise 32 bit | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows Server 2016 | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows Server 2012 Std | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows Server 2012 R2 Std | 3.7 | | 9.4 TS1M5 | |
64-bit Enabled Solaris | 3.7 | | 9.4 TS1M5 | |
64-bit Enabled AIX | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows Server 2012 R2 Datacenter | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows Server 2012 Datacenter | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows Server 2008 for x64 | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows Server 2008 R2 | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows Server 2008 | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows 10 | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows 8.1 Pro x64 | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows 8.1 Pro 32-bit | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows 8.1 Enterprise x64 | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows 8.1 Enterprise 32-bit | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows 8 Pro x64 | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows 8 Pro 32-bit | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows 8 Enterprise x64 | 3.7 | | 9.4 TS1M5 | |
Microsoft Windows 8 Enterprise 32-bit | 3.7 | | 9.4 TS1M5 | |
Microsoft® Windows® for x64 | 3.7 | | 9.4 TS1M5 | |
HP-UX IPF | 3.7 | | 9.4 TS1M5 | |
Linux for x64 | 3.7 | | 9.4 TS1M5 | |
Solaris for x64 | 3.7 | | 9.4 TS1M5 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2019-06-03 15:37:30 |
Date Created: | 2019-05-29 17:13:28 |