Problem Note 69800: SAS processes do not close properly after you apply the hot fix in SAS Note 67892
 |  |  |  |
If a SAS® Studio session stops without properly closing the associated SAS processes, the SAS Studio Server logs might contain the following error:
<datetime stamp> [ContainerBackgroundProcessor[StandardEngine[Catalina]]] ERROR com.sas.ep.sascoder.session.SessionManager - Unable to close rest session.
java.lang.Exception: InvalidSession
at com.sas.ep.sascoder.session.SessionManager.internalGetSession(SessionManager.java:144)
at com.sas.ep.sascoder.session.SessionManager.getSession(SessionManager.java:165)
at com.sas.ep.sascoder.session.SessionManager.closeSession(SessionManager.java:281)
at com.sas.ep.sascoder.session.SessionManager.cleanupRestSessionsForHttpSession(SessionManager.java:549)
at com.sas.ep.sascoder.session.SessionListener.sessionDestroyed(SessionListener.java:26)
at org.apache.catalina.session.StandardSession.expire(StandardSession.java:811)
at org.apache.catalina.session.StandardSession.isValid(StandardSession.java:669)
at org.apache.catalina.session.ManagerBase.processExpires(ManagerBase.java:576)
at org.apache.catalina.session.ManagerBase.backgroundProcess(ManagerBase.java:561)
at org.apache.catalina.core.StandardContext.backgroundProcess(StandardContext.java:5548)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1381)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1385)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1385)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1353)
at java.lang.Thread.run(Thread.java:748)
java.lang.Exception: InvalidSession
at com.sas.ep.sascoder.session.SessionManager.internalGetSession(SessionManager.java:144)
at com.sas.ep.sascoder.session.SessionManager.getSession(SessionManager.java:165)
at com.sas.ep.sascoder.session.SessionManager.closeSession(SessionManager.java:281)
at com.sas.ep.sascoder.session.SessionManager.cleanupRestSessionsForHttpSession(SessionManager.java:549)
at com.sas.ep.sascoder.session.SessionListener.sessionDestroyed(SessionListener.java:26)
at org.apache.catalina.session.StandardSession.expire(StandardSession.java:811)
at org.apache.catalina.session.StandardSession.isValid(StandardSession.java:669)
at org.apache.catalina.session.ManagerBase.processExpires(ManagerBase.java:576)
at org.apache.catalina.session.ManagerBase.backgroundProcess(ManagerBase.java:561)
at org.apache.catalina.core.StandardContext.backgroundProcess(StandardContext.java:5548)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1381)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1385)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1385)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1353)
at java.lang.Thread.run(Thread.java:748)
This problem is most likely to occur after you apply the hot fix in SAS Note 67892, “SAS® Studio contains a session hijacking vulnerability.”
There is no workaround for this issue.
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.81 | 9.4 TS1M7 | ||
| Microsoft Windows 8 Enterprise 32-bit | 3.81 | 9.4 TS1M7 | ||||
| Microsoft Windows 8 Enterprise x64 | 3.81 | 9.4 TS1M7 | ||||
| Microsoft Windows 8 Pro 32-bit | 3.81 | 9.4 TS1M7 | ||||
| Microsoft Windows 8 Pro x64 | 3.81 | 9.4 TS1M7 | ||||
| Microsoft Windows 8.1 Enterprise 32-bit | 3.81 | 9.4 TS1M7 | ||||
| Microsoft Windows 8.1 Enterprise x64 | 3.81 | 9.4 TS1M7 | ||||
| Microsoft Windows 8.1 Pro 32-bit | 3.81 | 9.4 TS1M7 | ||||
| Microsoft Windows 8.1 Pro x64 | 3.81 | 9.4 TS1M7 | ||||
| Microsoft Windows 10 | 3.81 | 9.4 TS1M7 | ||||
| Microsoft Windows 11 | 3.81 | 9.4 TS1M7 | ||||
| Microsoft Windows Server 2008 | 3.81 | 9.4 TS1M7 | ||||
| Microsoft Windows Server 2008 R2 | 3.81 | 9.4 TS1M7 | ||||
| Microsoft Windows Server 2008 for x64 | 3.81 | 9.4 TS1M7 | ||||
| Microsoft Windows Server 2012 Datacenter | 3.81 | 9.4 TS1M7 | ||||
| Microsoft Windows Server 2012 R2 Datacenter | 3.81 | 9.4 TS1M7 | ||||
| Microsoft Windows Server 2012 R2 Std | 3.81 | 9.4 TS1M7 | ||||
| Microsoft Windows Server 2012 Std | 3.81 | 9.4 TS1M7 | ||||
| Microsoft Windows Server 2016 | 3.81 | 9.4 TS1M7 | ||||
| Microsoft Windows Server 2019 | 3.81 | 9.4 TS1M7 | ||||
| Microsoft Windows Server 2022 | 3.81 | 9.4 TS1M7 | ||||
| Windows 7 Enterprise 32 bit | 3.81 | 9.4 TS1M7 | ||||
| Windows 7 Enterprise x64 | 3.81 | 9.4 TS1M7 | ||||
| Windows 7 Home Premium 32 bit | 3.81 | 9.4 TS1M7 | ||||
| Windows 7 Home Premium x64 | 3.81 | 9.4 TS1M7 | ||||
| Windows 7 Professional 32 bit | 3.81 | 9.4 TS1M7 | ||||
| Windows 7 Professional x64 | 3.81 | 9.4 TS1M7 | ||||
| Windows 7 Ultimate 32 bit | 3.81 | 9.4 TS1M7 | ||||
| Windows 7 Ultimate x64 | 3.81 | 9.4 TS1M7 | ||||
| 64-bit Enabled AIX | 3.81 | 9.4 TS1M7 | ||||
| 64-bit Enabled Solaris | 3.81 | 9.4 TS1M7 | ||||
| HP-UX IPF | 3.81 | 9.4 TS1M7 | ||||
| Linux for x64 | 3.81 | 9.4 TS1M7 | ||||
| Solaris for x64 | 3.81 | 9.4 TS1M7 | ||||
| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2023-01-19 11:22:28 |
| Date Created: | 2023-01-11 14:31:16 |