Problem Note 69660: A sign out from SAS® Studio 3.8 Enterprise might occur unexpectedly
 |  |  |  |  |
Programs in SAS Studio 3.8 that sometimes result in a log event payload that contains a very large number of log lines being sent to the SAS Studio middle tier can impact the performance and availability of the SAS® Web Application Server, SASServer2_1.
If SASServer2_1 is impacted by this issue and becomes unresponsive, a sign-out page with the following message might appear to anyone currently logged on to SAS Studio 3.8: "You have signed out." If you try to sign on after receiving this message, an HTTP 500 Internal Server Error message appears in the browser.
Click the Hot Fix tab in this note to access the hot fix for this issue.
The hot fix allows administrators to set a configuration option, webdms.maxLogLinesThreshold, to cap the maximum size (in terms of log lines) of a log event payload. If you set this configuration property to a specific value, the following warning is written to the log when the maximum threshold is exceeded, and streaming stops:
Streaming has been stopped.
Please contact your system administrator for assistance.
If you encounter the above warning, SAS recommends that you (or your administrator) adjust preferences according to the following Post-Hot-Fix Instructions.
Post-Hot-Fix Instructions
Important! These instructions apply to people whose programs have generated the above warning.
After you install the hot fix, a preference exists that changes the SAS Studio log behavior. To set the preference, select More application options ► Preferences ► Code and Log ► Log options ► Log update options. The options are as follows:
- Continuously stream updates to the log (Note: This is the default option.)
- Stream updates to the log when a procedure finishes
If you select this option, SAS Studio does not stream each line to the log as the code is completed. Instead, the log is cached and delivered to the SAS Studio log window when the program completes. In the event that a log exceeds one million lines, the following status message appears at the bottom of the log window:
WARNING: Maximum log size exceeded. Click here to view full log. - Stream updates to the log when submission completes
If you select this option, SAS Studio does not stream each line to the log as the code is completed. Instead, the log is cached and delivered to the SAS Studio log window when each procedure (or DATA step) completes. In the event that a log exceeds one million lines, the following status message appears at the bottom of the log window:
WARNING: Maximum log size exceeded. Click here to view full log.The log window opens in a new tab.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Studio | Microsoft® Windows® for x64 | 3.8 | 9.4 TS1M6 | ||
| Microsoft Windows 8 Enterprise 32-bit | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows 8 Enterprise x64 | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows 8 Pro 32-bit | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows 8 Pro x64 | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows 8.1 Enterprise 32-bit | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows 8.1 Enterprise x64 | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows 8.1 Pro 32-bit | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows 8.1 Pro x64 | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows 10 | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows Server 2008 | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows Server 2008 R2 | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows Server 2008 for x64 | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows Server 2012 Datacenter | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows Server 2012 R2 Datacenter | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows Server 2012 R2 Std | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows Server 2012 Std | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows Server 2016 | 3.8 | 9.4 TS1M6 | ||||
| Microsoft Windows Server 2019 | 3.8 | 9.4 TS1M6 | ||||
| Windows 7 Enterprise 32 bit | 3.8 | 9.4 TS1M6 | ||||
| Windows 7 Enterprise x64 | 3.8 | 9.4 TS1M6 | ||||
| Windows 7 Home Premium 32 bit | 3.8 | 9.4 TS1M6 | ||||
| Windows 7 Home Premium x64 | 3.8 | 9.4 TS1M6 | ||||
| Windows 7 Professional 32 bit | 3.8 | 9.4 TS1M6 | ||||
| Windows 7 Professional x64 | 3.8 | 9.4 TS1M6 | ||||
| Windows 7 Ultimate 32 bit | 3.8 | 9.4 TS1M6 | ||||
| Windows 7 Ultimate x64 | 3.8 | 9.4 TS1M6 | ||||
| 64-bit Enabled AIX | 3.8 | 9.4 TS1M6 | ||||
| 64-bit Enabled Solaris | 3.8 | 9.4 TS1M6 | ||||
| HP-UX IPF | 3.8 | 9.4 TS1M6 | ||||
| Linux for x64 | 3.8 | 9.4 TS1M6 | ||||
| Solaris for x64 | 3.8 | 9.4 TS1M6 | ||||
A fix for this issue for SAS Studio 3.82 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/M3T.html#69660A fix for this issue for SAS Studio 3.81 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/J7H.html#69660A fix for this issue for SAS Studio 3.8 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/D8F.html#69660| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2023-01-31 10:05:18 |
| Date Created: | 2022-11-03 12:04:52 |