Problem Note 58778: The SAS® Object Spawner stops launching Java client-initiated workspace servers that are doubly redirected
A SAS Object Spawner that has a load-balanced cluster of pooled workspace servers might stop responding and launching workspace servers for launch requests from an Integration Technologies client program based on Java.
The problem occurs when the request is redirected to another object spawner in the cluster, which then launches the actual workspace server. When the workspace server finishes its job and the Java client tries to close the connection, the close fails, and a file handle is left open. This eventually results in an error message in the SAS Object Spawner log:
The TCP/IP tcpSockAccept support routine failed with error 24 (Too many files are open.).
There is no workaround other than to restart the spawners.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Integration Technologies Client | Microsoft® Windows® for x64 | 9.31_M1 | | 9.3 TS1M2 | |
Microsoft Windows 8 Enterprise 32-bit | 9.31_M1 | | 9.3 TS1M2 | |
Microsoft Windows 8 Enterprise x64 | 9.31_M1 | | 9.3 TS1M2 | |
Microsoft Windows 8 Pro 32-bit | 9.31_M1 | | 9.3 TS1M2 | |
Microsoft Windows 8 Pro x64 | 9.31_M1 | | 9.3 TS1M2 | |
Microsoft Windows 8.1 Enterprise 32-bit | 9.31_M1 | | 9.3 TS1M2 | |
Microsoft Windows 8.1 Enterprise x64 | 9.31_M1 | | 9.3 TS1M2 | |
Microsoft Windows 8.1 Pro 32-bit | 9.31_M1 | | 9.3 TS1M2 | |
Microsoft Windows 8.1 Pro x64 | 9.31_M1 | | 9.3 TS1M2 | |
Microsoft Windows Server 2003 Datacenter Edition | 9.31_M1 | | 9.3 TS1M2 | |
Microsoft Windows Server 2003 Enterprise Edition | 9.31_M1 | | 9.3 TS1M2 | |
Microsoft Windows Server 2003 Standard Edition | 9.31_M1 | | 9.3 TS1M2 | |
Microsoft Windows Server 2003 for x64 | 9.31_M1 | | 9.3 TS1M2 | |
Microsoft Windows Server 2008 | 9.31_M1 | | 9.3 TS1M2 | |
Microsoft Windows Server 2008 R2 | 9.31_M1 | | 9.3 TS1M2 | |
Microsoft Windows Server 2008 for x64 | 9.31_M1 | | 9.3 TS1M2 | |
Microsoft Windows Server 2012 Datacenter | 9.31_M1 | | 9.3 TS1M2 | |
Microsoft Windows Server 2012 R2 Datacenter | 9.31_M1 | | 9.3 TS1M2 | |
Microsoft Windows Server 2012 R2 Std | 9.31_M1 | | 9.3 TS1M2 | |
Microsoft Windows Server 2012 Std | 9.31_M1 | | 9.3 TS1M2 | |
Microsoft Windows XP Professional | 9.31_M1 | | 9.3 TS1M2 | |
Windows 7 Enterprise 32 bit | 9.31_M1 | | 9.3 TS1M2 | |
Windows 7 Enterprise x64 | 9.31_M1 | | 9.3 TS1M2 | |
Windows 7 Home Premium 32 bit | 9.31_M1 | | 9.3 TS1M2 | |
Windows 7 Home Premium x64 | 9.31_M1 | | 9.3 TS1M2 | |
Windows 7 Professional 32 bit | 9.31_M1 | | 9.3 TS1M2 | |
Windows 7 Professional x64 | 9.31_M1 | | 9.3 TS1M2 | |
Windows 7 Ultimate 32 bit | 9.31_M1 | | 9.3 TS1M2 | |
Windows 7 Ultimate x64 | 9.31_M1 | | 9.3 TS1M2 | |
Windows Vista | 9.31_M1 | | 9.3 TS1M2 | |
Windows Vista for x64 | 9.31_M1 | | 9.3 TS1M2 | |
*
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: | 2016-09-14 09:57:55 |
Date Created: | 2016-08-12 08:43:12 |